summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbikebilly <fabio@gitlab.com>2018-06-18 14:39:20 -0400
committerbikebilly <fabio@gitlab.com>2018-06-18 14:39:20 -0400
commit7b1c34732317d9df8d17bbd85aa26a1c02623156 (patch)
treec8d02ebd248d5b9754d3cc38d1559514125c65c9
parentf0607059b6a2b87cda36c70b2bce30d11e18bd3c (diff)
downloadgitlab-ce-7b1c34732317d9df8d17bbd85aa26a1c02623156.tar.gz
Copyedits
-rw-r--r--PROCESS.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/PROCESS.md b/PROCESS.md
index bbb239800ad..c730cb918d9 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -240,7 +240,8 @@ available in the package repositories.
Regressions are very important, and they should be considered high priority
issues that should be solved as soon as possible, especially if they affect
-users. Despite that, ~regression label itself is not a [priority label].
+users. Despite that, ~regression label itself is not implying when the issue
+will be scheduled.
When a regression is found:
1. Create an issue describing the problem in the most detailed way possible
@@ -335,4 +336,3 @@ still an issue I encourage you to open it on the [GitLab.com issue tracker](http
[done]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#definition-of-done
[automatic_ce_ee_merge]: https://docs.gitlab.com/ce/development/automatic_ce_ee_merge.html
[ee_features]: https://docs.gitlab.com/ce/development/ee_features.html
-[priority label]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#priority-labels-deliverable-stretch-next-patch-release