summaryrefslogtreecommitdiff
path: root/doc/development/labels/index.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/labels/index.md')
-rw-r--r--doc/development/labels/index.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/development/labels/index.md b/doc/development/labels/index.md
index af4df4adee2..50b6ec74575 100644
--- a/doc/development/labels/index.md
+++ b/doc/development/labels/index.md
@@ -233,8 +233,7 @@ release. There are three levels of Release Scoping labels:
milestone. If these issues are not done in the current release, they will
strongly be considered for the next release.
- `~"Next Patch Release"`: Issues to put in the next patch release. Work on these
- first, and add the `~"Pick into X.Y"` label to the merge request, along with the
- appropriate milestone.
+ first, and follow the [patch release runbook](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/engineers.md) to backport the bug fix to the current version.
Each issue scheduled for the current milestone should be labeled `~"Deliverable"~`
or `~"Stretch"`. Any open issue for a previous milestone should be labeled