Update release checklist (#7329)

Signed-off-by: Simon Dudley <simon.dudley@consensys.net>
pull/7352/head
Simon Dudley 4 months ago committed by GitHub
parent 39e276fd10
commit 592acb7b50
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
  1. 20
      .github/ISSUE_TEMPLATE/release-checklist.md

@ -8,8 +8,8 @@ assignees: ''
--- ---
- [ ] Confirm anything outstanding for release with other maintainers on #besu-release in Discord - [ ] Confirm anything outstanding for release with other maintainers on #besu-release in Discord
- [ ] Update changelog if necessary, and merge a PR for it to main
- [ ] Notify maintainers about updating changelog for in-flight PRs - [ ] Notify maintainers about updating changelog for in-flight PRs
- [ ] Update changelog if necessary, and merge a PR for it to main
- [ ] Optional: for hotfixes, create a release branch and cherry-pick, e.g. `release-<version>-hotfix` - [ ] Optional: for hotfixes, create a release branch and cherry-pick, e.g. `release-<version>-hotfix`
- [ ] Optional: create a PR into main from the hotfix branch to see the CI checks pass - [ ] Optional: 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` - [ ] On the appropriate branch/commit, create a calver tag for the release candidate, format example: `24.4.0-RC2`
@ -18,18 +18,14 @@ assignees: ''
- [ ] Sign off burn-in; convey burn-in results in #besu-release in Discord - [ ] Sign off burn-in; convey burn-in results in #besu-release in Discord
- [ ] Using the same git sha, create a calver tag for the FULL RELEASE, example format `24.4.0` - [ ] 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: - [ ] Using the FULL RELEASE tag, create a release in github to trigger the workflows. Once published:
- makes the release "latest" in github
- this is now public and notifies subscribed users - this is now public and notifies subscribed users
- makes the release "latest" in github
- publishes artefacts and version-specific docker tags - publishes artefacts and version-specific docker tags
- publishes the docker `latest` tag variants - publishes the docker `latest` tag variants
- [ ] Draft homebrew PR - [ ] Check binary SHAs are correct on the release page
- [ ] Draft documentation release - [ ] Check "Container Verify" GitHub workflow has run successfully
- [ ] Ensure binary SHAs are correct on the release page - [ ] Create homebrew release - run https://github.com/hyperledger/homebrew-besu/actions/workflows/update-version.yml
- [ ] Docker release startup test: - [ ] Create besu-docs release - https://github.com/hyperledger/besu-docs/releases/new
- `docker run hyperledger/besu:<version>` - Copy release notes from besu
- `docker run hyperledger/besu:<version>-arm64` - 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
- `docker run --platform linux/amd64 hyperledger/besu:<version>-amd64`
- `docker run --pull=always hyperledger/besu:latest` (check version is <version>)
- [ ] Merge homebrew PR
- [ ] Publish Docs Release
- [ ] Social announcements - [ ] Social announcements

Loading…
Cancel
Save