summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMek Stittri <mstittri@gitlab.com>2018-06-28 08:01:54 -0700
committerMek Stittri <mstittri@gitlab.com>2018-06-28 16:12:42 -0700
commite681bb83016cbbeb4d3953749f01efef978597d7 (patch)
treebd0f83b394c803d77382e7bcdf117c850ec4a1d4
parent6c533e0ebfa46ba5e5eaf676c03a9e193d808c3a (diff)
downloadgitlab-ce-regression-label.tar.gz
Add excerpt for non-regressionsregression-label
-rw-r--r--PROCESS.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/PROCESS.md b/PROCESS.md
index eb694197890..f9baf8676d5 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -228,6 +228,8 @@ A ~regression label on a ~bug tells us that something worked before and it needs
The milestone of a ~regression is used to schedule when the fix will be delivered. The creation time of a ~regression tells us which release it was found in.
+A ~regression label does not apply to ~bugs for new features. That by the definition above are not regressions.
+
## Release retrospective and kickoff
- [Retrospective](https://about.gitlab.com/handbook/engineering/workflow/#retrospective)