Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Cc: bugzilla@g.o
Subject: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED
Date: Thu, 16 Jun 2016 13:02:30
Message-Id: 20160616150213.47f09bc4.mgorny@gentoo.org
1 Hello, everyone.
2
3 Here's the third bugs.g.o redesign RFC.
4
5 This time it's about closed bugs. Right now we have two states for
6 them: RESOLVED and VERIFIED.
7
8 RESOLVED is the usual state that the developers use when they close
9 a bug. It's also the only state that could be directly transferred from
10 other states.
11
12 VERIFIED is used scarcely, and not really consistently. It can only be
13 used on RESOLVED bugs, and sometimes users use it to confirm that
14 the bug is resolved.
15
16 To be honest, I don't really see the need for VERIFIED state. Since
17 it's used scarcely, it can't be really relied upon. Some users use it
18 completely incorrectly (e.g. when the bug should be reopened instead).
19
20 What I'd like to introduce instead is a new STABILIZED state. It would
21 -- like VERIFIED now -- be only available for bugs already RESOLVED,
22 and it could be used to signify that the fix has made it into stable.
23
24 While this wouldn't be really obligatory, it would be meaningful for
25 trackers that need to ensure that fixes in packages have made it to
26 stable -- like the functions.sh use tracker.
27
28 --
29 Best regards,
30 Michał Górny
31 <http://dev.gentoo.org/~mgorny/>

Replies