summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVictor Wu <victor@gitlab.com>2017-04-13 22:16:54 +0000
committerVictor Wu <victor@gitlab.com>2017-04-13 22:16:54 +0000
commit34b0197778271dd2f65d16763d0b6456766f0175 (patch)
tree5ec7bcc355cae69f8182809e6e33ac5c52a0ccb2
parent530d17f1e207fe60d0e854fa57fb02f7c0ea4ca6 (diff)
downloadgitlab-ce-34b0197778271dd2f65d16763d0b6456766f0175.tar.gz
Remove unnecessary example.
-rw-r--r--PROCESS.md2
1 files changed, 0 insertions, 2 deletions
diff --git a/PROCESS.md b/PROCESS.md
index 3efbb8f83ab..cfa841dc13d 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -139,8 +139,6 @@ When in doubt, we err on the side of _not_ cherry-picking.
For example, it is likely that an exception will be made for a trivial 1-5 line performance improvement
(e.g. adding a database index or adding `includes` to a query), but not for a new feature, no matter how relatively small or thoroughly tested.
-Another exception example is a medium-risk feature such as a navigation change in response to significant negative community feedback from a previous release.
-
During the feature freeze all merge requests that are meant to go into the upcoming
release should have the correct milestone assigned _and_ have the label
~"Pick into Stable" set, so that release managers can find and pick them.