summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFabio Busatto <fabio@gitlab.com>2018-03-05 16:42:24 +0000
committerbikebilly <fabio@gitlab.com>2018-06-18 08:44:14 -0400
commitb272518db3574ee6d2577e3f31d6b98563278d1e (patch)
tree20bc573d2a9abb43e908bb6ab51c64a4e717e857
parent8f335b27b04d1a862f654cd99cce0f5ee98b63af (diff)
downloadgitlab-ce-b272518db3574ee6d2577e3f31d6b98563278d1e.tar.gz
Copyedit
-rw-r--r--PROCESS.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/PROCESS.md b/PROCESS.md
index 5fdab3ed382..6da55b632fe 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -250,7 +250,8 @@ When a regression is found:
and any other label that may apply in the specific case
3. Add the ~regression label
4. Add the proper milestone
-4. Ping the Product Manager, see [product categories](https://about.gitlab.com/handbook/product/categories/)
+4. Ping the Product Manager for proper scheduling, see
+ [product categories](https://about.gitlab.com/handbook/product/categories/)
to find who manages that specific area of the Product
A very important step is helping the PM to understand the impact the regression