Creates a new issue template for releases #6972
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,38 @@ | ||||||||||
| --- | ||||||||||
| name: Release Checklist | ||||||||||
| about: items to be completed for each release | ||||||||||
| title: '' | ||||||||||
| labels: '' | ||||||||||
| assignees: '' | ||||||||||
|
|
||||||||||
| --- | ||||||||||
|
|
||||||||||
| - [ ] Confirm anything outstanding for release with other maintainers on #besu-release | ||||||||||
| - [ ] Update changelog if necessary | ||||||||||
| - [ ] Notify maintainers about updating changelog for in-flight PRs | ||||||||||
| - [ ] Optional: for hotfixes, create a release branch and cherry-pick, e.g. `release-<version>-hotfix` | ||||||||||
| - [ ] Optional: create a PR against 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 | ||||||||||
| - [ ] Create a DRAFT release using the new tag (careful not to publish!) | ||||||||||
| - [ ] Draft homebrew PR | ||||||||||
| - [ ] Draft documentation release | ||||||||||
| - [ ] Sign-off with team | ||||||||||
| - [ ] Start burn-in using the new <version-RCX> tag | ||||||||||
| - [ ] Sign off burn-in | ||||||||||
| - [ ] Convert the DRAFT into a PRE-RELEASE | ||||||||||
| - this is now public and notifies subscribed users | ||||||||||
| - publishes artefacts and version-specific docker tags | ||||||||||
| - [ ] Using the same git sha, create a new tag for the FULL RELEASE, example format 24.4.0 | ||||||||||
| - [ ] Using the FULL RELEASE tag, create a PRE-RELEASE in github to trigger the workflows | ||||||||||
|
There was a problem hiding this comment. does this mean we get 2 pre-releases? one for the RC and one for the full release tag? There was a problem hiding this comment. this is copypasta from @siladu but i interpreted it as using pre-release is optional for RCs There was a problem hiding this comment. ok fair enough. DCO is broken tho There was a problem hiding this comment. This is the part I asked for feedback on. This is also in flux due to #6963 There was a problem hiding this comment.
Suggested change
Moving extra comments from the removed step above |
||||||||||
| - [ ] Convert this to a FULL RELEASE | ||||||||||
| - makes the release LATEST in github | ||||||||||
| - publishes the docker `latest` tag variants | ||||||||||
| - [ ] Ensure binary SHAs are correct on the release page | ||||||||||
| - [ ] Docker release startup test: | ||||||||||
| - `docker run hyperledger/besu:<version>` | ||||||||||
| - `docker run hyperledger/besu:<version>-arm64` | ||||||||||
| - `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 | ||||||||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have removed this step from the WIP checklist as it would result in creating redundant 24.5.0-RC1 artefacts.
See #6963 (comment) for context.
Most of the time we will want to go straight from draft/burn-in -> full release, with pre-release being a necessary in-between step for now. That pre-release needs to use the full release tag e.g. 24.5.0 instead of 24.5.0-RC1.