summaryrefslogtreecommitdiff
path: root/PROCESS.md
diff options
context:
space:
mode:
authorbikebilly <fabio@gitlab.com>2018-06-18 08:53:51 -0400
committerbikebilly <fabio@gitlab.com>2018-06-18 08:53:51 -0400
commitf0607059b6a2b87cda36c70b2bce30d11e18bd3c (patch)
tree7b254aa99ad77c168c1d0622b4c619a532679891 /PROCESS.md
parent07d1a7f012a6e04b5b36712685cccfb95e6dc1c4 (diff)
downloadgitlab-ce-f0607059b6a2b87cda36c70b2bce30d11e18bd3c.tar.gz
Update regression labeling
Diffstat (limited to 'PROCESS.md')
-rw-r--r--PROCESS.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/PROCESS.md b/PROCESS.md
index 23f800d70f5..bbb239800ad 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -253,8 +253,9 @@ When a regression is found:
1. Evaluate the priority and add a [Priority label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#bug-priority-labels-p1-p2-p3-p4)
1. Schedule the issue in order to get it fixed as soon as possible, based on severity and priority, following these guidelines:
- If the regression is ~S1 or ~S2, 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"
+ - 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"
+ - If the regression is ~S3 or ~S4, it can be scheduled for later milestones
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