Gentoo Archives: gentoo-dev

From: Christian Ruppert <idl0r@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Bugzilla - New Default Status Workflow
Date: Sun, 01 May 2011 09:39:48
Message-Id: 4DBD2A36.6020007@gentoo.org
In Reply to: Re: [gentoo-dev] Bugzilla - New Default Status Workflow by Christian Ruppert
1 On 04/30/2011 10:40 AM, Christian Ruppert wrote:
2 > On 04/28/2011 04:07 PM, Christian Ruppert wrote:
3 >> So once again:
4 >>
5 >> https://bugs.gentoo.org/docs/en/html/lifecycle.html
6 >>
7 >> *Every* new bug filed by a user without editbugs will have "UNCONFIRMED"
8 >> (old NEW) as fixed status.
9 >> *If* we don't enable the UNCONFIRMED status at all then it will
10 >> CONFIRMED as default but we would enable the UNCONFIRMED status.
11 >>
12 >> Bug wranglers can then assign the bug and they also *can* mark it as
13 >> CONFIRMED *if* they *can* confirm it.
14 >> The maintainer may change the status to IN_PROGRESS (old ASSIGNED)
15 >> afterwards.
16 >>
17 >> The snipped of my first mail may be a bit confusing... It just means:
18 >> NEW will become CONFIRMED, NEW has been fully replaced by CONFIRMED so
19 >> NEW is gone but CONFIRMED is *not* the new default status. CONFIRMED
20 >> would/could be the default for everybody with editbugs.
21 >> ASSIGNED gone, replacement: IN_PROGRESS,
22 >> REOPENED gone,
23 >> CLOSED gone. VERIFIED will be added.
24 >>
25 >> So I think we should convert...
26 >>
27 >
28 > I think I'll convert the workflow in about 24h if nobody really
29 > complains. There is more positive feedback anyway.
30 >
31
32 Done. The new workflow is online.
33
34 --
35 Regards,
36 Christian Ruppert
37 Role: Gentoo Linux developer, Bugzilla administrator and Infrastructure
38 member
39 Fingerprint: EEB1 C341 7C84 B274 6C59 F243 5EAB 0C62 B427 ABC8

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] Bugzilla - New Default Status Workflow Christian Ruppert <idl0r@g.o>