You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current release process seems out of order and requires maintainers to run commands locally with a personal access token.
Out of order
Updating the changelog comes after cutting the release.
The PR to update the changelog is a good opportunity to double check the contents of the release, and review how each change is framed for consumers. I think we should make sure we do this prior to tagging the release.
* This includes a PR to update CHANGELOG.md as the first step in the process
* The rest of the process is managed in the Github releases workflow, which
* Input a tag that will be created on publish
* Click a button to generate release notes from CHANGELOG.md
* Publish a tag and the release anouncement in a single step
* No local commands required
This is the most natural workflow in my opinion.
For what it is worth, I do the same when releasing opentelemetry-cpp.
The current release process seems out of order and requires maintainers to run commands locally with a personal access token.
Out of order
Updating the changelog comes after cutting the release.
The PR to update the changelog is a good opportunity to double check the contents of the release, and review how each change is framed for consumers. I think we should make sure we do this prior to tagging the release.
Requires maintainers to run commands locally
See steps here:
https://github.com/open-telemetry/opentelemetry-configuration/blame/16452629a3f119af3d1fa74a17c9f85ad5076119/RELEASING.md#L26-L46
Proposal
Follow the release process from
opentelemetry-proto
: https://github.com/open-telemetry/opentelemetry-proto/blob/main/RELEASING.mdThe text was updated successfully, but these errors were encountered: