open-telemetry
/
opentelemetry-collector
mirror of https://github.com/open-telemetry/opentelemetry-collector.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update release.md after 0.48.0 release (#5132) 

Updated instructions and the schedule.
This commit is contained in:
Tigran Najaryan 2022-03-31 12:09:56 -04:00 committed by GitHub
parent 699a81b216
commit 02ac059ec4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/release.md
View File

@ -38,7 +38,7 @@ It is possible that a core approver isn't a contrib approver. In that case, the
* Update CHANGELOG.md file and rename the Unreleased section to the new release name. Add a new unreleased section at top. Use commit history feature to get the list of commits since the last release to help understand what should be in the release notes, e.g.: https://github.com/open-telemetry/opentelemetry-collector/compare/v0.44.0...main.
* Use multimod to update the version of the collector package
* Update [versions.yaml](https://github.com/open-telemetry/opentelemetry-collector/blob/main/versions.yaml) and commit it
* Update [versions.yaml](https://github.com/open-telemetry/opentelemetry-collector/blob/main/versions.yaml) and commit it locally
* Run `make multimod-prerelease` (it might fail if you didn't commit the change above)
* Update the collector version in the collector builder to the new release in `./cmd/builder/internal/builder/config.go`.
@ -57,7 +57,7 @@ It is possible that a core approver isn't a contrib approver. In that case, the
1. The release script for the collector builder should create a new GitHub release for the builder. This is a separate release from the core, but we might join them in the future if it makes sense.
1. Create a new `v0.45.0` release and use the contents from the CHANGELOG.md as the release's description. At the top of the release's changelog, add a link to the releases repository where the binaries and other artifacts are landing, like:
1. A new `v0.45.0` release should be automatically created on Github by now. Edit it and use the contents from the CHANGELOG.md as the release's description. At the top of the release's changelog, add a link to the releases repository where the binaries and other artifacts are landing, like:
```
### Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.45.0
@ -67,7 +67,7 @@ It is possible that a core approver isn't a contrib approver. In that case, the
1. Prepare Contrib for release.
* Update CHANGELOG.md file and rename the Unreleased section to the new release name. Add a new unreleased section at top. Refer to Core release notes (assuming the previous release of Core and Contrib was also performed simultaneously), and in addition to that list changes that happened in the Contrib repo.
* Update CHANGELOG.md file and rename the Unreleased section to the new release name. Add a new unreleased section at top.
* Use multimod to update the version of the collector package:
@ -81,7 +81,7 @@ It is possible that a core approver isn't a contrib approver. In that case, the
1. Tag all the modules with the new release version by running the `make add-tag TAG=v0.45.0` command. Push them to `open-telemetry/opentelemetry-collector-contrib` with `make push-tag TAG=v0.45.0`. Wait for the new tag build to pass successfully.
1. Create a new `v0.45.0` release and use the contents from the CHANGELOG.md as the release's description.
1. A new `v0.45.0` release should be automatically created on Github by now. Edit it and use the contents from the CHANGELOG.md as the release's description. At the top of the description add a link to Core release notes (assuming the previous release of Core and Contrib was also performed simultaneously), e.g. "The OpenTelemetry Collector Contrib contains everything in the [opentelemetry-collector release](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.45.0) (be sure to check the release notes here as well!)."
## Producing the artifacts
@ -109,10 +109,10 @@ The last step of the release process creates artifacts for the new version of th
| Date | Version | Release manager |
|------------|---------|-----------------|
| 2022-03-30 | v0.48.0 | @tigrannajaryan |
| 2022-04-13 | v0.49.0 | @dmitryax |
| 2022-04-27 | v0.50.0 | @codeboten |
| 2022-05-11 | v0.51.0 | @bogdandrutu |
| 2022-05-25 | v0.52.0 | @jpkrohling |
| 2022-06-01 | v0.53.0 | @Aneurysm9 |
| 2022-06-15 | v0.54.0 | @mx-psi |
| 2022-06-29 | v0.55.0 | @tigrannajaryan |