diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-16 00:08:46 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-16 00:08:46 +0000 |
| commit | cc93ae5beb8a50c959373b77a9fdd6b31a88f00c (patch) | |
| tree | b203d2fefffb1d78b653282de554d26d50a0d75b /.gitlab/merge_request_templates/Removals.md | |
| parent | 2b5079efdb7c4e7d5a607d95747ddeb0b8af9678 (diff) | |
| download | gitlab-ce-cc93ae5beb8a50c959373b77a9fdd6b31a88f00c.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to '.gitlab/merge_request_templates/Removals.md')
| -rw-r--r-- | .gitlab/merge_request_templates/Removals.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/.gitlab/merge_request_templates/Removals.md b/.gitlab/merge_request_templates/Removals.md index 5b4c8473d1d..39b99c00314 100644 --- a/.gitlab/merge_request_templates/Removals.md +++ b/.gitlab/merge_request_templates/Removals.md @@ -46,7 +46,6 @@ Please review: - [ ] Set yourself as the Assignee, meaning you are the DRI. - [ ] If the removal is a [breaking change](https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-change), add label `breaking change`. - [ ] Follow the process to [create a removal YAML file](https://about.gitlab.com/handbook/marketing/blog/release-posts/#creating-a-removal-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. - Removal notices should not be merged before the code is removed from the product. Do not mark ~ready until the removal is complete, or you are certain it will be completed within the current milestone and released. If PMs are not sure, they should confirm with their Engineering Manager. |