summaryrefslogtreecommitdiff
path: root/PROCESS.md
diff options
context:
space:
mode:
authorMichael Kozono <mkozono@gmail.com>2018-06-08 18:00:51 +0000
committerMichael Kozono <mkozono@gmail.com>2018-06-08 18:00:51 +0000
commit19020d3cb3655928529bda9294aa4e51a5149eef (patch)
treea6480d64224e3c845ce169f03148bd146b6a0d76 /PROCESS.md
parent8cd6ffab51acade21f793103d4fedf6c04a20496 (diff)
downloadgitlab-ce-19020d3cb3655928529bda9294aa4e51a5149eef.tar.gz
Remove unnecessary and broken examplemk/remove-unnecessary-and-broken-example-docs
The example provided was broken because it mistakes a bug for a regression. It is not needed for clarity anyway. The milestone part is no longer relevant as well.
Diffstat (limited to 'PROCESS.md')
-rw-r--r--PROCESS.md6
1 files changed, 1 insertions, 5 deletions
diff --git a/PROCESS.md b/PROCESS.md
index 7438df8014b..958bc7b9edc 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -185,11 +185,7 @@ next patch release.
If a merge request is to be picked into more than one release it will need one
`Pick into X.Y` label per release where the merge request should be back-ported
-to.
-
-For example, if the current patch release is `10.1.1` and a regression fix needs
-to be backported down to the `9.5` release, you will need to assign it the
-`10.1` milestone and the following labels:
+to. For example:
- `Pick into 10.1`
- `Pick into 10.0`