From 33551cf273f81309dd906a4b17521220f3f23d20 Mon Sep 17 00:00:00 2001 From: Mayra Cabrera Date: Wed, 29 Nov 2023 16:01:50 -0600 Subject: [PATCH] Remove milestone requirement from security MR template Related to https://gitlab.com/gitlab-org/release-tools/-/merge_requests/2805/ --- .gitlab/merge_request_templates/Security Release.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/.gitlab/merge_request_templates/Security Release.md b/.gitlab/merge_request_templates/Security Release.md index 3d0fe1f9a..b394c8c87 100644 --- a/.gitlab/merge_request_templates/Security Release.md +++ b/.gitlab/merge_request_templates/Security Release.md @@ -13,7 +13,6 @@ See [the general developer security release guidelines](https://gitlab.com/gitla - [ ] **On "Related issues" section, write down the [Omnibus GitLab Security] issue it belongs to (i.e. `Related to `).** - [ ] MR targets `master`, or `X-Y-stable` for backports. -- [ ] Milestone is set for the version this merge request applies to. A closed milestone can be assigned via [quick actions]. - [ ] Title of this MR is the same as for all backports. - [ ] A [CHANGELOG entry] has been included, with `Changelog` trailer set to `security`. - [ ] Assign to a reviewer and maintainer, per our [Code Review process]. @@ -23,7 +22,6 @@ See [the general developer security release guidelines](https://gitlab.com/gitla ## Reviewer checklist -- [ ] Correct milestone is applied and the title is matching across all backports - [ ] Assigned to `@gitlab-release-tools-bot` with passing CI pipelines /label ~security