summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbikebilly <fabio@gitlab.com>2018-06-18 08:38:16 -0400
committerbikebilly <fabio@gitlab.com>2018-06-18 08:44:16 -0400
commit2e88192bb329353630207ef7843e0c47ea11519b (patch)
treec763c5706d7dd1f15a4256f1b92858601f031488
parentd7db1fd597abe4aa1228b944be8884306292aae0 (diff)
downloadgitlab-ce-2e88192bb329353630207ef7843e0c47ea11519b.tar.gz
Update regression labeling
-rw-r--r--PROCESS.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/PROCESS.md b/PROCESS.md
index ccde094412f..a1c2337be0c 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -249,11 +249,11 @@ When a regression is found:
the [subject label](../CONTRIBUTING.md#subject-labels-wiki-container-registry-ldap-api-etc)
and any other label that may apply in the specific case
1. Add the ~bug and ~regression labels
+1. Evaluate the Severity of the regression and add a Severity level
1. Add the proper milestone and priority label:
- - If the issue is for a feature that was introduced in the previous release.
- label with the previous milestone and ~"Next Patch Release"
- - If the issue is for a feature that is introduced in a RC version for the
- current release, label with the current milestone and ~"Deliverable"
+ - If the regression is ~S1 or ~S2, label set the current milestone
+ - If the regression was introduced in a RC of the current release, label with ~Deliverable
+ - If the regression was introduced in the previos release, label with ~"Next Patch Release"
When a new issue is found, the fix should start as soon as possible. You can
ping the Engineering Manager or the Product Manager for the relative area to