-
Notifications
You must be signed in to change notification settings - Fork 353
Move release instructions to RELEASING.md #1762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| # Making a Release | ||
|
|
||
| - Ensure the referenced specification version is up to date. Use | ||
| [tooling to update the spec](./CONTRIBUTING.md#updating-the-referenced-specification-version) | ||
| if needed. | ||
| - Run [opentelemetry.io workflow](https://github.com/open-telemetry/opentelemetry.io/actions/workflows/build-dev.yml) | ||
| against `semantic-conventions` submodule as a smoke-test for docs. Fix broken links, if any. | ||
| - Create a staging branch for the release. | ||
| - Update `schema-next.yaml` file and move to `schemas/{version}` | ||
| - Ensure the `next` version is appropriately configured as the `{version}`. | ||
| - Copy `schema-next.yaml` to `schemas/{version}`. | ||
| - Add `next` as a version in `schema-next.yaml` version. | ||
| - Run `make chlog-update VERSION=v{version}` | ||
| - `make chlog-update` will clean up all the current `.yaml` files inside the | ||
| `.chloggen` folder automatically | ||
| - Double check that `CHANGELOG.md` is updated with the proper `v{version}` | ||
| - Send staging branch as PR for review. | ||
| - After the release PR is merged, create a [new release](https://github.com/open-telemetry/semantic-conventions/releases/new): | ||
| - Set title and tag to `v{version}` | ||
| - Set target to the commit of the merged release PR | ||
| - Copy changelog to the release notes | ||
| - Verify that the release looks like expected | ||
| - Publish release | ||
|
|
||
| New release is then auto-discovered by [opentelemetry.io](https://github.com/open-telemetry/opentelemetry.io) pipelines which (via bot-generated PR) | ||
| eventually results in new version of schema file being published. | ||
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.
Uh oh!
There was an error while loading. Please reload this page.