You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .gitlab/issue_templates/Security developer workflow.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,13 +24,14 @@ After your merge request has been approved according to our approval guidelines,
24
24
#### Backports
25
25
26
26
-[ ] Once the MR is ready to be merged, create MRs targeting the latest 3 stable branches
27
+
* The 3 stable branches correspond to the versions in the title of the [Security Release Tracking Issue].
27
28
* At this point, it might be easy to squash the commits from the MR into one
28
29
* Depending on when development is happening, you may need to wait for the last stable branch to be created. If the ~"security-notifications" label is applied to this issue, you will receive a ping when the branch is created.
29
30
-[ ] Create each MR targeting the stable branch `X-Y-stable`, using the [Security Release merge request template].
30
31
* Every merge request will have its own set of TODOs, so make sure to complete those.
31
32
-[ ] On the "Related merge requests" section, ensure all MRs are linked to this issue.
32
33
* This section should only list the merge requests created for this issue: One targeting `master` and the 3 backports.
33
-
-[ ] If this issue requires less than 4 merge requests, post a message on the Security Release Tracking Issue and ping the Release Managers.
34
+
-[ ] If this issue requires less than `4` merge requests, add the ~"reduced backports" label.
34
35
35
36
#### Assigning to a release
36
37
@@ -68,5 +69,6 @@ After your merge request has been approved according to our approval guidelines,
0 commit comments