summaryrefslogtreecommitdiff
path: root/PROCESS.md
diff options
context:
space:
mode:
authorMek Stittri <mstittri@gitlab.com>2018-06-26 23:59:44 -0700
committerMek Stittri <mstittri@gitlab.com>2018-07-26 23:56:11 -0700
commit8680038c9f8edfe00955f8e80bec195a75070aa8 (patch)
treed55cafb2b4768e7b9689498049e3d15c1355872c /PROCESS.md
parent13ea4b387ddcee5f5e8a59ac90dc9e485f4242f5 (diff)
downloadgitlab-ce-8680038c9f8edfe00955f8e80bec195a75070aa8.tar.gz
Clarrify use of regression label
Diffstat (limited to 'PROCESS.md')
-rw-r--r--PROCESS.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/PROCESS.md b/PROCESS.md
index a06ddb68b77..af66a343f13 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -244,6 +244,12 @@ ping the Engineering Manager or the Product Manager for the relative area to
make them aware of the issue earlier. They will analyze the priority and change
it if needed.
+A ~regression label implies that a regress in functionality happened, a functionality which worked previously but no longer works currently.
+The ~regression label is not removed as part of the "Rescheduling" process. If an issue is indeed a regression, it should carry such context forward until it's fully resolved.
+A ~regression label on a ~bug tells us that something worked before and it needs extra attention from Engineering and Product Managers to schedule/reschedule.
+
+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.
+
## Release retrospective and kickoff
- [Retrospective](https://about.gitlab.com/handbook/engineering/workflow/#retrospective)