Create release tag early for greater clarity

This way, it's clearer in the repo what is going to be released, and we don't need to copy/paste commit IDs.

([skip ci] because this branch only touches .md file)
This commit is contained in:
David Cook
2023-08-15 21:38:04 +10:00
parent 1cd87c170b
commit b320a1d289

View File

@@ -19,17 +19,22 @@ assignees: ''
git commit -a -m "Update all locales with the latest Transifex translations"
git push upstream master</pre>
</details>
- [ ] Create a tag:
<details><summary>Command line instructions:</summary>
<pre>
git tag vX.X.X
git push upstream vX.X.X</pre>
</details>
- [ ] [Draft new release]. Look at previous [releases] for inspiration.
- Select latest master commit
- Select new release tag
- _Generate release notes_ and arrange into categories as required.
- [ ] Notify [#instance-managers] of user-facing changes.
## 2. Testing
- [ ] Copy the release commit below
- [ ] Move this issue to Test Ready.
- [ ] Notify `@testers` in [#testing].
- [ ] Test build: [Deploy to Staging] with commit <!-- paste commit ID here, eg bb8bcecc9... -->
- [ ] Test build: [Deploy to Staging] with release tag.
## 3. Finish on Tuesday