From a4bac1f8c3b83d481ae12f5808fdf2d1e0b74ff3 Mon Sep 17 00:00:00 2001 From: Michael Kozono Date: Mon, 16 Apr 2018 17:14:40 +0000 Subject: Clarify bug vs regression --- PROCESS.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/PROCESS.md b/PROCESS.md index f206506f7c5..c210dfdcf97 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -228,7 +228,9 @@ have a milestone, it might be 'just' a bug! For instance, if 10.5.0 adds a feature, and that feature doesn't work correctly, then this is a regression in 10.5. If 10.5.1 then fixes that, but 10.5.3 somehow -reintroduces the bug, then this bug is still a regression in 10.5. +reintroduces the bug, then this bug is still a regression in 10.5. If the +upcoming release is 10.6-RC1, and the fix is not yet merged, then the bug no +longer counts as a regression. Because GitLab.com runs release candidates of new releases, a regression can be reported in a release before its 'official' release date on the 22nd of the -- cgit v1.2.1