From ce450dea2740bebd7dd6b1a1ab96221dd1c3247d Mon Sep 17 00:00:00 2001 From: zeme Date: Thu, 20 Jun 2024 14:13:05 +0200 Subject: [PATCH] Update RELEASE.adoc with instructions to delete unused branches and tags --- RELEASE.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/RELEASE.adoc b/RELEASE.adoc index 797060bd304..338efcda56e 100644 --- a/RELEASE.adoc +++ b/RELEASE.adoc @@ -98,6 +98,10 @@ Another example is if a security audit is done on `rc1`, and the changes in `rc2 - This will automatically open a PR in `plutus-tx-template` with auto-merge enabled - Ensure that CI is green and the PR gets merged +10. 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`. @@ -113,6 +117,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