Skip to content

Commit ac137b3

Browse files
Remove Feature Freeze from document statuses. (#4575)
Follow up to #4529 Discussed this recently during the Specification call and there was initial agreement regarding removing Feature Freeze (and potentially restoring it if needed). PS - embarrassed to realize we had forgotten to remove Feature freeze from the Baggage API and Context documents.
1 parent 9b2d7c8 commit ac137b3

File tree

4 files changed

+3
-9
lines changed

4 files changed

+3
-9
lines changed

oteps/metrics/0146-metrics-prototype-scenarios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ before end of 2021:
1515
We might introduce additional features but there should be a high bar.
1616

1717
* By end of 9/30/2021, we should mark the metrics API/SDK specification as
18-
[`Feature-freeze`](../../specification/document-status.md#feature-freeze),
18+
`Feature-freeze`,
1919
and focus on bug fixing or editorial changes.
2020

2121
* By end of 11/30/2021, we want to have a stable release of metrics API/SDK

specification/baggage/api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Baggage API
22

3-
**Status**: [Stable, Feature-freeze](../document-status.md)
3+
**Status**: [Stable](../document-status.md)
44

55
<details>
66
<summary>Table of Contents</summary>

specification/context/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ path_base_for_github_subdir:
77

88
# Context
99

10-
**Status**: [Stable, Feature-freeze](../document-status.md).
10+
**Status**: [Stable](../document-status.md).
1111

1212
<details>
1313
<summary>Table of Contents</summary>

specification/document-status.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,6 @@ The specification follows
2424
[OTEP 0232](../oteps/0232-maturity-of-otel.md#explanation)
2525
maturity level definitions.
2626

27-
## Feature freeze
28-
29-
In addition to the maturity levels above, documents may be marked as `Feature-freeze`. These documents are not currently accepting new feature requests, to allow the Technical Committee time to focus on other areas of the specification. Editorial changes are still accepted. Changes that address production issues with existing features are still accepted.
30-
31-
Feature freeze is separate from a maturity level. The maturity level represents the support requirements for the document, feature freeze only indicates the current focus of the specification community. The feature freeze label may be applied to a document at any maturity level. By definition, deprecated documents have a feature freeze in place.
32-
3327
## Mixed
3428

3529
Some documents have individual sections with different statuses. These documents are marked with the status `Mixed` at the top, for clarity.

0 commit comments

Comments
 (0)