Skip to content
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

dev-docs: make post release steps more prominent #3497

Merged
merged 1 commit into from
Nov 26, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions dev-docs/workflows/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,8 @@ Releases should be performed using [the automated release pipeline](https://gith
6. look over the autogenerated draft release. When fixing the changelog, prioritize updating the PR title/labels/description and regenerating the changelog over fixing things in the final changelog. The changelog should be primarily aimed at users. Rule of thumb: first part of the sentence should describe what changed for the user, second part can describe what has been changed to achieve this.
7. in the GitHub release UI, make sure the tag to create on release is set to `$ver`, and the target commit is set to the temporary release branch.
8. publish.
9. follow [post release steps](#post-release-steps).


### Minor release

Expand Down Expand Up @@ -78,6 +80,7 @@ Releases should be performed using [the automated release pipeline](https://gith
8. set the Target to `tmp/${ver}`
9. in the GitHub release UI, make sure the tag to create on release is set to `$ver`, and the target commit is set to the temporary release branch.
10. publish.
11. follow [post release steps](#post-release-steps).

## Post release steps

Expand Down
Loading