From 46b27b2d9d03e5567c1b3ba05004e97b3f77e7d4 Mon Sep 17 00:00:00 2001 From: David Cook Date: Tue, 18 Jul 2023 09:34:28 +1000 Subject: [PATCH] Number release steps There are three distinct parts to the process, so I thought it worth giving them an identifying number. --- .github/ISSUE_TEMPLATE/release.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release.md b/.github/ISSUE_TEMPLATE/release.md index 81872029cb..0361542676 100644 --- a/.github/ISSUE_TEMPLATE/release.md +++ b/.github/ISSUE_TEMPLATE/release.md @@ -7,21 +7,21 @@ assignees: '' --- -## Preparation on Thursday +## 1. Preparation on Thursday - [ ] Merge pull requests in the [Ready To Go] column - [ ] Include translations: `tx pull --force` - [ ] [Draft new release]. Look at previous [releases] for inspiration. - [ ] Notify [#instance-managers] of user-facing changes. -## Testing +## 2. Testing - [ ] [Find build] of the release commit and copy it below. - [ ] Move this issue to Test Ready. - [ ] Notify `@testers` in [#testing]. - [ ] Test build: -## Finish on Tuesday +## 3. Finish on Tuesday - [ ] Publish and notify [#global-community] (this is automatically posted with a plugin) - [ ] Deploy the new release to all managed instances.