Update documentation for how to cut a release AND perform the action … #190
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
…for the 1.21.0 release. This will become the commit we tag for 1.21
4 tasks
reyang
reviewed
Jul 13, 2023
reyang
approved these changes
Jul 13, 2023
There was a problem hiding this comment.
LGTM, https://github.com/open-telemetry/semantic-conventions/pull/190/files#r1261832861 doesn't have to be a blocker for the release cut.
arminru
approved these changes
Jul 13, 2023
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
rapphil
pushed a commit
to rapphil/semantic-conventions
that referenced
this pull request
Aug 14, 2023
open-telemetry#190) Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
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.
…for the 1.21.0 release. This will become the commit we tag for 1.21.
Fixes #37 #136
Note: I think there's some better automation and checks we can do for
schema-next.yamland setting the version numbers on release going forward.