gitlab-org--gitlab-foss/.gitlab/merge_request_templates/Security Release.md
Yorick Peterse 02412a5040
Update the MR template for security MRs
This makes two changes to the template:

1. EE MRs are now always required (see
   https://gitlab.com/gitlab-org/release/framework/issues/256 for a
   backstory).

2. We clarify that a release manager is not a suitable reviewer for
   security merge requests.
2019-03-27 13:35:28 +01:00

1.4 KiB

Developer checklist

  • Link to the developer security workflow issue on dev.gitlab.org
  • MR targets master, or X-Y-stable for backports
  • Milestone is set for the version this MR applies to
  • Title of this MR is the same as for all backports
  • A CHANGELOG entry is added without a merge_request value, with type set to security
  • Add a link to this MR in the links section of related issue
  • Set up an EE MR (always required for CE merge requests): EE_MR_LINK_HERE
  • Assign to a reviewer (that is not a release manager)

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