diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-15 21:10:04 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-15 21:10:04 +0300 |
commit | 5ff1f808adf841bca979cb2fac6bdfa9c449d028 (patch) | |
tree | c95cfbbcb400684b2bc89fee4fc7b614315ba909 /doc/development/labels | |
parent | f8a5275c45ed2276daf843764113476749e680d2 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/labels')
-rw-r--r-- | doc/development/labels/index.md | 3 |
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 |