diff options
Diffstat (limited to '.gitlab/merge_request_templates/Deprecations.md')
| -rw-r--r-- | .gitlab/merge_request_templates/Deprecations.md | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/.gitlab/merge_request_templates/Deprecations.md b/.gitlab/merge_request_templates/Deprecations.md index 8f1d7363a42..841ef70d92a 100644 --- a/.gitlab/merge_request_templates/Deprecations.md +++ b/.gitlab/merge_request_templates/Deprecations.md @@ -1,10 +1,5 @@ <!-- Set the correct label and milestone using autocomplete for guidance. Please @mention only the DRI(s) for each stage or group rather than an entire department. --> -/label ~"release post" ~"release post item" ~"Technical Writing" ~devops:: ~group:: ~"release post item::deprecation" -/label ~"type::maintenance" -/milestone % -/assign `@EM/PM` (choose the DRI; remove backticks here, and below) - **Be sure to link this MR to the relevant deprecation issue(s).** - Deprecation Issue: @@ -42,10 +37,12 @@ They are frequently updated, and everyone should make sure they are aware of the - [ ] Set yourself as the Assignee, meaning you are the DRI. - [ ] If the deprecation is a [breaking change](https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-change), add label `breaking change`. +- [ ] Confirm this MR is labeled ~"release post item::deprecation" - [ ] Follow the process to [create a deprecation YAML file](https://about.gitlab.com/handbook/marketing/blog/release-posts/#creating-a-deprecation-entry). -- [ ] Make sure that the milestone dates are based on the dates in [Product milestone creation](https://about.gitlab.com/handbook/product/milestones/#product-milestone-creation). - [ ] Add reviewers by the 10th. -- [ ] When ready to be merged and not later than the 15th, add the `~ready` label and @ message the TW for final review and merge. +- [ ] Add scoped `devops::` and `group::` labels as necessary. +- [ ] Add the appropriate milestone to this MR. +- [ ] When ready to be merged (and no later than the 15th) `@mention` the TW for final review and merge. ## Reviewers @@ -106,3 +103,7 @@ must be updated before this MR is merged: 1. Set the MR to merge when the pipeline succeeds (or merge if the pipeline is already complete). If you have trouble running the Rake task, check the [troubleshooting steps](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecation-rake-task-troubleshooting). + +/label ~"release post" ~"release post item" ~"Technical Writing" ~"release post item::deprecation" +/label ~"type::maintenance" +/label ~"maintenance::refactor" |