debian-mirror-gitlab/.gitlab/issue_templates/Security Release Tracking Issue.md

42 lines
1.3 KiB
Markdown
Raw Normal View History

2019-05-05 18:10:48 +05:30
<!--
# Read me first!
2019-10-12 21:52:04 +05:30
Set the title to: `Security Release: 12.2.X, 12.1.X, and 12.0.X`
2019-05-05 18:10:48 +05:30
-->
2020-04-08 14:13:33 +05:30
:warning: **Only Release Managers and members of the AppSec team can edit the description of this issue**
-------
2019-05-05 18:10:48 +05:30
## Version issues:
2020-04-08 14:13:33 +05:30
12.2.X, 12.1.X, 12.0.X: {release task link}
2019-05-05 18:10:48 +05:30
2020-03-13 15:44:24 +05:30
## Issues in GitLab Security
2019-05-05 18:10:48 +05:30
2020-04-08 14:13:33 +05:30
To include your issue and merge requests in this Security Release, please mark
your security issues as related to this release tracking issue. You can do this
in the "Linked issues" section below this issue description.
2019-05-05 18:10:48 +05:30
2020-04-08 14:13:33 +05:30
:warning: If your security issues are not marked as related to this release
2020-10-24 23:57:45 +05:30
tracking issue, their merge requests will not be included in the security
2020-04-08 14:13:33 +05:30
release.
2019-05-05 18:10:48 +05:30
2020-10-24 23:57:45 +05:30
### Branches to target in GitLab Security
Your Security Implementation Issue should have `4` merge requests associated:
- [master and 3 backports](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/security/developer.md#backports)
- Backports should target the stable branches for the versions mentioned included in this Security Release
2019-05-05 18:10:48 +05:30
## Blog post
Dev: {https://dev.gitlab.org/gitlab/www-gitlab-com/merge_requests/ link}<br/>
2020-03-13 15:44:24 +05:30
GitLab.com: {https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/ link}
2019-05-05 18:10:48 +05:30
## Email notification
{https://gitlab.com/gitlab-com/marketing/general/issues/ link}
2020-04-08 14:13:33 +05:30
/label ~security ~"upcoming security release"
2019-05-05 18:10:48 +05:30
/confidential