## Problem/motivation Follow-up from: #3586321+s It would be useful to have an issue template for the release process. ## Solution Make this into an issue template: - [ ] Finish all issues from the release planning and milestone, e.g. #3586182+ - [ ] Run a code review (at least a security review) for major issues, e.g. #3586294+ - [ ] Resolve any blockers from the code review - [ ] Code freeze - [ ] Run manual QA, e.g. #3586296+ - [ ] Resolve any blockers from QA - [ ] Re-run security review if there were changes - [ ] Re-run QA if there were changes - [ ] Code freeze - [ ] Move closed issues from future milestone to current (e.g. beta4 to beta3) - [ ] Audit contributors (code is happening here: #3586222+) - [ ] Create release notes (code is happening here: #3586222+) - [ ] Create release, e.g. #3586295+ - [ ] Create post-release promotion issues, e.g. #3577657+, #3586154+ - [ ] Create recruit testers issue, e.g. #3586235+ - [ ] Announce in various Slack channels