debian-mirror-gitlab/.gitlab/merge_request_templates/Security Release.md

38 lines
1.9 KiB
Markdown
Raw Normal View History

2019-05-05 18:10:48 +05:30
<!--
# README first!
2020-03-07 23:17:34 +05:30
This MR should be created on `gitlab.com/gitlab-org/security/gitlab`.
2019-05-05 18:10:48 +05:30
See [the general developer security release guidelines](https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/developer.md).
-->
2020-03-07 23:17:34 +05:30
2019-05-05 18:10:48 +05:30
## Related issues
2020-03-07 23:17:34 +05:30
<!-- Mention the GitLab Security issue this MR is related to -->
2019-05-05 18:10:48 +05:30
## Developer checklist
2020-04-08 14:13:33 +05:30
- [ ] **On "Related issues" section, write down the [GitLab Security] issue it belongs to (i.e. `Related to <issue_id>`).**
2020-03-07 23:17:34 +05:30
- [ ] Merge request 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 merge request is the same as for all backports.
2019-05-05 18:10:48 +05:30
- [ ] A [CHANGELOG entry](https://docs.gitlab.com/ee/development/changelog.html) is added without a `merge_request` value, with `type` set to `security`
2020-03-07 23:17:34 +05:30
- [ ] Assign to a reviewer and maintainer, per our [Code Review process].
- [ ] For the MR targeting `master`:
- [ ] Ping appsec team member who created the issue and ask for a non-blocking review with `Please review this MR`.
- [ ] Ensure it's approved according to our [Approval Guidelines].
- [ ] Merge request _must not_ close the corresponding security issue, _unless_ it targets `master`.
2019-05-05 18:10:48 +05:30
2020-03-07 23:17:34 +05:30
**Note:** Reviewer/maintainer should not be a Release Manager
2019-05-05 18:10:48 +05:30
2020-03-07 23:17:34 +05:30
## Maintainer checklist
2019-05-05 18:10:48 +05:30
- [ ] Correct milestone is applied and the title is matching across all backports
2020-04-22 19:07:51 +05:30
- [ ] Assigned to `@gitlab-release-tools-bot` with passing CI pipelines and **when all backports including the MR targeting master are ready.**
2019-05-05 18:10:48 +05:30
/label ~security
2020-03-07 23:17:34 +05:30
[GitLab Security]: https://gitlab.com/gitlab-org/security/gitlab
[approval guidelines]: https://docs.gitlab.com/ee/development/code_review.html#approval-guidelines
[Code Review process]: https://docs.gitlab.com/ee/development/code_review.html
[quick actions]: https://docs.gitlab.com/ee/user/project/quick_actions.html#quick-actions-for-issues-merge-requests-and-epics