Add release process issue template #2818
Open
Conversation
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
A Github issue template to help formalizing the release process, in order to avoid human errors in the process. Closes: damus-io#2752 Signed-off-by: Daniel D’Aquino <[email protected]>
|
@alltheseas, @jb55, please let me know if you have any suggestions for the release process. Thank you! |
|
On Wed, Jan 22, 2025 at 02:15:37PM GMT, Daniel D’Aquino wrote:
A Github issue template to help formalizing the release process, in
order to avoid human errors in the process.
Closes: #2752
Signed-off-by: Daniel D’Aquino ***@***.***>
---
LGTM
Reviewed-by: William Casarin ***@***.***>
|
|
Looks good overall! Question - does it make sense to add a question/step in the process "Check with devs & product - are there release showstoppers (e.g. critical newfound bug)?" |
jb55
approved these changes
Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
A Github issue template to help formalizing the release process, in order to avoid human errors in the process.
I captured the checklist used for the 1.12 release into this issue template, to help us stay consistent with this process.
Closes: #2752
Checklist
Closes:orFixes:tags in the commit messages wherever applicable, or made sure those are not needed. See Submitting patchesTest report
We used this checklist during the 1.12 release (#2772), which I believe captures everything we need.
Results: