Gentoo Archives: gentoo-dev

From: Andrew Savchenko <bircoph@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] bugs.g.o: Merging UNCONFIRMED & CONFIRMED into NEW
Date: Thu, 16 Jun 2016 13:22:45
Message-Id: 20160616162232.3f292d44480870b9ac0b2ec3@gentoo.org
In Reply to: [gentoo-dev] [RFC] bugs.g.o: Merging UNCONFIRMED & CONFIRMED into NEW by "Michał Górny"
1 On Thu, 16 Jun 2016 14:26:47 +0200 Michał Górny wrote:
2 > Hello, everyone.
3 >
4 > Here's my second RFC wrt bugs.gentoo.org redesign.
5 >
6 > Right now we have separate UNCONFIRMED and CONFIRMED states for bugs.
7 > However, we use the two scarcely. I believe it would be beneficial to
8 > replace the two with a single NEW state.
9 >
10 > Rationale:
11 >
12 > 1. Most of developers don't care about the two states, and which one
13 > bugs are in.
14 >
15 > 2. All bugs need to be handled the same, whether they were marked as
16 > confirmed or not.
17 >
18 > 3. We stage bugs through bug-wranglers@ which kinda has a similar
19 > purpose to the UNCONFIRMED state in other Bugzillas.
20 >
21 > 4. Some people who actually care about the two states change them,
22 > causing unnecessary bugspam.
23 >
24 > 5. Some users who think that the state matters get furious about bugs
25 > staying in UNCONFIRMED for long.
26 >
27 > Your thoughts?
28
29 CONFIRMED state is useful, it means that dev or powerful user
30 confirmed this bug and gives it more value. I'd like to keep it.
31
32 Best regards,
33 Andrew Savchenko

Replies