diff options
author | Marcel Amirault <mamirault@gitlab.com> | 2023-07-24 13:21:16 +0300 |
---|---|---|
committer | Marcel Amirault <mamirault@gitlab.com> | 2023-07-24 13:21:16 +0300 |
commit | 8cf2bf82ac870b1362afae4de8bb2ccfac366559 (patch) | |
tree | db37d569df9455b3c143290ae19ed3c7ca977487 /.gitlab/issue_templates | |
parent | 9643571e27099b72b9ac08ff68bfc76594e1ed3e (diff) |
Update release issue template
Diffstat (limited to '.gitlab/issue_templates')
-rw-r--r-- | .gitlab/issue_templates/release.md | 15 |
1 files changed, 7 insertions, 8 deletions
diff --git a/.gitlab/issue_templates/release.md b/.gitlab/issue_templates/release.md index 4a1fc647..2ecc39b3 100644 --- a/.gitlab/issue_templates/release.md +++ b/.gitlab/issue_templates/release.md @@ -25,7 +25,7 @@ The following terms are used throughout this document: ```markdown ## :+1: What went well this release? - ## :-1: What didn’t go well this release? + ## :-1: What didn't go well this release? ## :chart_with_upwards_trend: What can we improve going forward? ``` @@ -80,19 +80,18 @@ After the release post is live on the 22nd, or the next Monday morning if the re 1. [ ] After the deployment completes, open `docs.gitlab.com` in a browser. Confirm both the latest version and the correct pre-release version are listed in the documentation version dropdown. 1. [ ] Check all published versions of the docs to ensure they are visible and that their version menus have the latest versions. -1. [ ] Mention `@gl-docsteam` in a comment and invite them to read and participate in the retro threads. +1. [ ] Share the following message in the `#tw-team` channel: - ```markdown - @gl-docsteam here's the docs release issue for XX.ZZ with some retro threads, per our [process](#on-the-22nd-or-the-first-business-day-after). + ```plaintext + :mega: The docs <version> release is complete. If you have any feedback about this release, add it to the retro thread in <this issue>. ``` After the 22nd of each month: -1. [ ] Create a release issue for the - [next TW](https://about.gitlab.com/handbook/product/ux/technical-writing/#regularly-scheduled-tasks) - and assign it to them. +1. [ ] Create a release issue for the next release, and assign it to the TW who completed the + [release post structural check for the previous milestone](https://about.gitlab.com/handbook/product/ux/technical-writing/#regularly-scheduled-tasks). 1. [ ] **Major releases only.** Update - [OutdatedVersions.yml](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale/gitlab/OutdatedVersions.yml) + [`OutdatedVersions.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale/gitlab/OutdatedVersions.yml) with the newly-outdated version. 1. [ ] Improve this checklist. Continue moving steps from [`releases.md`](https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/doc/releases.md) |