summaryrefslogtreecommitdiff
path: root/PROCESS.md
diff options
context:
space:
mode:
authorFabio Busatto (OOO until 19/3) <fabio@gitlab.com>2018-03-14 14:30:58 +0000
committerbikebilly <fabio@gitlab.com>2018-06-18 08:44:16 -0400
commitd7db1fd597abe4aa1228b944be8884306292aae0 (patch)
tree4f1d0ceb4091dda9c1bb48fad72a928d098a414c /PROCESS.md
parent34f47303005640acd912712944780b02cf219cb6 (diff)
downloadgitlab-ce-d7db1fd597abe4aa1228b944be8884306292aae0.tar.gz
Explain milestone usage
Diffstat (limited to 'PROCESS.md')
-rw-r--r--PROCESS.md18
1 files changed, 11 insertions, 7 deletions
diff --git a/PROCESS.md b/PROCESS.md
index 4e8fec32041..ccde094412f 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -244,17 +244,21 @@ users. Despite that, ~regression label itself is not a [priority label].
When a regression is found:
1. Create an issue describing the problem in the most detailed way possible
+1. If possible, provide links to real examples and how to reproduce the problem
1. Label the issue properly, using the [team label](../CONTRIBUTING.md#team-labels-ci-discussion-edge-platform-etc),
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. Add the proper milestone
-1. If possible, provide links to real examples and how to reproduce the problem
-
-Feel free to put ~"Next Patch Release" label to the issue so the fix can start
-as soon as possible. You can 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 take proper actions if needed.
+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"
+
+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
+make them aware of the issue earlier. They will analyze the priority and change
+it if needed.
## Release retrospective and kickoff