Apply new stability definitions to this repo #4051
Labels
spec:miscellaneous
For issues that don't match any other spec label
triage:accepted:ready
Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
Comments
tigrannajaryan
added
the
spec:miscellaneous
|
if it helps, I suspect that the existing usages of "Feature Freeze" in this repo could probably be removed |
|
I agree with both the mapping and removing feature-freeze. |
dyladan
added
the
triage:accepted:ready
tigrannajaryan
added a commit
to tigrannajaryan/opentelemetry-specification
that referenced
this issue
May 27, 2024
Resolves open-telemetry#4051 [OTEP 0232](https://github.com/open-telemetry/oteps/blob/main/text/0232-maturity-of-otel.md) brought new stability definitions. The impact on this repository is that we need to rename "Experimental" to "Development". All other existing statuses remain unchanged. Note: OTEP 0232 also introduces other levels, such as Alpha, Beta, etc. We will need to decide separately if we want to start using these level in this repository.
tigrannajaryan
added a commit
that referenced
this issue
Jun 4, 2024
Resolves #4051 [OTEP 0232](https://github.com/open-telemetry/oteps/blob/main/text/0232-maturity-of-otel.md) brought new stability definitions. The impact on this repository is that we need to rename "Experimental" to "Development". All other existing statuses remain unchanged. Note: OTEP 0232 also introduces other levels, such as Alpha, Beta, etc. We will need to decide separately if we want to start using these levels in this repository.
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 31, 2024
…etry#4061) Resolves open-telemetry#4051 [OTEP 0232](https://github.com/open-telemetry/oteps/blob/main/text/0232-maturity-of-otel.md) brought new stability definitions. The impact on this repository is that we need to rename "Experimental" to "Development". All other existing statuses remain unchanged. Note: OTEP 0232 also introduces other levels, such as Alpha, Beta, etc. We will need to decide separately if we want to start using these levels in this repository.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OTEP 0232 brought new stability definitions.
We need to apply those to this repository.
I think the following mapping is reasonable, but would like other opinions too:
Question: do we need to map "Feature Freeze" to some OTEP 0232 level, e.g. "Release Candidate"?
The text was updated successfully, but these errors were encountered: