diff options
| author | Steve Abrams <sabrams@gitlab.com> | 2023-11-17 21:13:24 +0300 |
|---|---|---|
| committer | Steve Abrams <sabrams@gitlab.com> | 2023-11-17 21:13:24 +0300 |
| commit | b374853a484727cc363f70696f76e41cc8acda0b (patch) | |
| tree | b215bbd45e98472257722a3ab5ad6eab879cc3cc | |
| parent | e66f6ec5ad5b47cb43e69a4690c3e9e1a9a49b4e (diff) | |
Link security tracking issue in the security issue template
| -rw-r--r-- | .gitlab/issue_templates/Security Release.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/Security Release.md b/.gitlab/issue_templates/Security Release.md index f468ca29d..6de2b23fa 100644 --- a/.gitlab/issue_templates/Security Release.md +++ b/.gitlab/issue_templates/Security Release.md @@ -24,12 +24,14 @@ After your merge request has been approved according to our [approval guidelines ## Backports - [ ] Once the MR is ready to be merged, create MRs targeting the latest 3 stable branches + * The 3 stable branches correspond to the versions in the title of the [Security Release Tracking Issue]. * At this point, it might be easy to squash the commits from the MR into one * You can use the script `bin/secpick` instead of the following steps, to help you cherry-picking. See the [secpick documentation] - [ ] Create each MR targeting the stable branch `X-Y-stable`, using the [Security Release merge request template]. * Every merge request will have its own set of TODOs, so make sure to complete those. - [ ] On the "Related merge requests" section, ensure all MRs are linked to this issue. * This section should only list the merge requests created for this issue: One targeting `master` and the 3 backports. +- [ ] If this issue requires less than `4` merge requests, add the ~"reduced backports" label. ## Assigning to a release @@ -66,5 +68,6 @@ After your merge request has been approved according to our [approval guidelines [code review process]: https://docs.gitlab.com/ee/development/code_review.html [approval guidelines]: https://docs.gitlab.com/ee/development/code_review.html#approval-guidelines [issue as related]: https://docs.gitlab.com/ee/user/project/issues/related_issues.html#adding-a-related-issue +[Security Release Tracking Issue]: https://gitlab.com/gitlab-org/gitlab/-/issues/?label_name%5B%5D=upcoming%20security%20release /label ~"devops::systems" ~"group::gitaly" ~"security" ~"security-notifications" |