Add upgrading and version management documentation #3695
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trask
approved these changes
Sep 19, 2023
tigrannajaryan
approved these changes
Sep 19, 2023
This comment was marked as duplicate.
This comment was marked as duplicate.
Sorry, something went wrong.
marcalff
reviewed
Sep 20, 2023
carlosalberto
approved these changes
Sep 20, 2023
|
Overall LGTM - although I'm curious around the 1-year deprecation phase, mostly as we haven't, so far, deprecated any Plugin component. |
jsuereth
approved these changes
Sep 20, 2023
|
Editorial: any chance to limit the line lengths? Commenting on a specific word/sentence is harder and github diffs are less readable with very long lines. |
MrAlias
reviewed
Sep 21, 2023
MrAlias
reviewed
Sep 21, 2023
MrAlias
reviewed
Sep 21, 2023
MrAlias
approved these changes
Sep 21, 2023
This was referenced Sep 26, 2023
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
1 task
Merged
arminru
added a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 10, 2023
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 31, 2024
Long ago, we defined upgrading procedures for OpenTelemetry, in [OTEP 147](https://github.com/open-telemetry/oteps/blob/main/text/0147-upgrade-procedures.md). However, we never added this language to the specification. This pull request adds the OTEP to the specification, verbatim, except for an addition at the top which clearly spells out dependency management for application developers, library maintainers, and SDK implementors. It has been two years, so I am open to changes to this document. Both for clarity, and to conform to how we currently practice upgrading and dependency management.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Long ago, we defined upgrading procedures for OpenTelemetry, in OTEP 147. However, we never added this language to the specification.
This pull request adds the OTEP to the specification, verbatim, except for an addition at the top which clearly spells out dependency management for application developers, library maintainers, and SDK implementors.
It has been two years, so I am open to changes to this document. Both for clarity, and to conform to how we currently practice upgrading and dependency management.