summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMek Stittri <mstittri@gitlab.com>2018-06-28 08:01:54 -0700
committerMek Stittri <mstittri@gitlab.com>2018-07-26 23:56:11 -0700
commited79f338aa74859cd5e554e8948432d6156d847d (patch)
tree13f9f74faa954feba5dd4174b9d400cf8b4db608
parent8680038c9f8edfe00955f8e80bec195a75070aa8 (diff)
downloadgitlab-ce-ed79f338aa74859cd5e554e8948432d6156d847d.tar.gz
Add excerpt for non-regressions
-rw-r--r--PROCESS.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/PROCESS.md b/PROCESS.md
index af66a343f13..ef25efb61ff 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -250,6 +250,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)