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.

Sign up for GitHub

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

Jump to bottom

Update RELEASE.adoc with instructions to delete unused branches and tags #6230

Merged
merged 1 commit into from
Jun 21, 2024
Merged

Update RELEASE.adoc with instructions to delete unused branches and tags #6230

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 5 additions & 0 deletions RELEASE.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,10 @@ Another example is if a security audit is done on `rc1`, and the changes in `rc2
- Click the `Run workflow` button on the right, enter the new release version and confirm
- Ensure that the action completes successfully

11. Delete unused brances and tags
- If it was created, delete the `release/*` branch locally and on GitHub
- If they were created, delete any release candidate `-rc*` tags locally and on GitHub

=== Patch Releases

Suppose we are releasing version `x.y.z.w`.
Expand All @@ -118,6 +122,7 @@ If so, create branch `release/x.y.z` from the `x.y.z.0` tag.
6. Open a PR for updating the cabal files and the changelog files.
7. Once the PR is merged, tag the commit `x.y.z.w`, and open a PR in the CHaP repository for publishing the new version.
- If issues are found, fix them on master, backport the fixes to `release/x.y.z`, and go to step 5.
8. If it was created, delete the `release/*` branch locally and on GitHub

=== Release QA Process

Expand Down