From cafe82d2d56085da31ab9d3a46c0a5320f85f615 Mon Sep 17 00:00:00 2001 From: Sally MacFarlane Date: Fri, 16 Aug 2024 11:37:10 +1000 Subject: [PATCH] clarification for release steps (#7400) * clarification for release steps Signed-off-by: Sally MacFarlane * PR feedback Signed-off-by: Sally MacFarlane * burn-in signoff Signed-off-by: Sally MacFarlane * added items Signed-off-by: Sally MacFarlane --------- Signed-off-by: Sally MacFarlane Co-authored-by: Simon Dudley --- .github/ISSUE_TEMPLATE/release-checklist.md | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release-checklist.md b/.github/ISSUE_TEMPLATE/release-checklist.md index 9840a3fa49..721c26edbd 100644 --- a/.github/ISSUE_TEMPLATE/release-checklist.md +++ b/.github/ISSUE_TEMPLATE/release-checklist.md @@ -11,11 +11,16 @@ assignees: '' - [ ] Update changelog if necessary, and merge a PR for it to main - [ ] Notify maintainers about updating changelog for in-flight PRs - [ ] Optional: for hotfixes, create a release branch and cherry-pick, e.g. `release--hotfix` -- [ ] Optional: create a PR into main from the hotfix branch to see the CI checks pass + - [ ] Optional: for hotfixes, create a PR into main from the hotfix branch to see the CI checks pass - [ ] On the appropriate branch/commit, create a calver tag for the release candidate, format example: `24.4.0-RC2` -- [ ] Sign-off with team; confirm tag is correct in #besu-release in Discord -- [ ] Consensys staff start burn-in using the proposed release tag -- [ ] Sign off burn-in; convey burn-in results in #besu-release in Discord + - [ ] git tag 24.4.0-RC2 + - [ ] git push upstream 24.4.0-RC2 +- [ ] Sign-off with team; announce the tag in #besu-release in Discord + - [ ] Targeting this tag for the burn-in: https://github.com/hyperledger/besu/releases/tag/24.4.0-RC2 +- [ ] Consensys staff start burn-in using this tag +- [ ] Seek sign off for burn-in + - [ ] Pass? Go ahead and complete the release process + - [ ] Fail? Put a message in #besu-release in Discord indicating the release will be aborted because it failed burn-in - [ ] Using the same git sha, create a calver tag for the FULL RELEASE, example format `24.4.0` - [ ] Using the FULL RELEASE tag, create a release in github to trigger the workflows. Once published: - this is now public and notifies subscribed users @@ -24,8 +29,9 @@ assignees: '' - publishes the docker `latest` tag variants - [ ] Check binary SHAs are correct on the release page - [ ] Check "Container Verify" GitHub workflow has run successfully -- [ ] Create homebrew release - run https://github.com/hyperledger/homebrew-besu/actions/workflows/update-version.yml - [ ] Create besu-docs release - https://github.com/hyperledger/besu-docs/releases/new - - Copy release notes from besu - - If publishing the release in github doesn't automatically trigger this workflow, then manually run https://github.com/hyperledger/besu-docs/actions/workflows/update-version.yml + - Copy release notes from besu + - If publishing the release in github doesn't automatically trigger this workflow, then manually run https://github.com/hyperledger/besu-docs/actions/workflows/update-version.yml +- [ ] Create homebrew release - run GHA workflow directly https://github.com/hyperledger/homebrew-besu/actions/workflows/update-version.yml +- [ ] Delete the burn-in nodes (unless required for further analysis eg performance) - [ ] Social announcements