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

Update releasing doc (#6911) 

Something I learned today...
This commit is contained in:
Trask Stalnaker 2022-10-19 03:56:35 -07:00 committed by GitHub
parent 6fb1f00241
commit 7ec441bb3a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
RELEASING.md
View File

@ -41,6 +41,10 @@ and deadlocks.
e.g. `release/v1.9.x`, then enter the pull request number that you want to backport,
then click the "Run workflow" button below that.
* Review and merge the backport pull request that it generates.
* Note: if the PR contains any changes to workflow files, it will have to be manually backported,
because the default `GITHUB_TOKEN` does not have permission to update workflow files (and the
`opentelemetrybot` token doesn't have write permission to this repository at all, so while it
can be used to open a PR, it can't be used to push to a local branch).
* Merge a pull request to the release branch updating the `CHANGELOG.md`.
* The heading for the unreleased entries should be `## Unreleased`.
* Run the [Prepare patch release workflow](https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/workflows/prepare-patch-release.yml).