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: Sat, 30 Apr 2011 08:41:00
Message-Id: 4DBBCAEB.2080107@gentoo.org
In Reply to: Re: [gentoo-dev] Bugzilla - New Default Status Workflow by Christian Ruppert
1 On 04/28/2011 04:07 PM, Christian Ruppert wrote:
2 > So once again:
3 >
4 > https://bugs.gentoo.org/docs/en/html/lifecycle.html
5 >
6 > *Every* new bug filed by a user without editbugs will have "UNCONFIRMED"
7 > (old NEW) as fixed status.
8 > *If* we don't enable the UNCONFIRMED status at all then it will
9 > CONFIRMED as default but we would enable the UNCONFIRMED status.
10 >
11 > Bug wranglers can then assign the bug and they also *can* mark it as
12 > CONFIRMED *if* they *can* confirm it.
13 > The maintainer may change the status to IN_PROGRESS (old ASSIGNED)
14 > afterwards.
15 >
16 > The snipped of my first mail may be a bit confusing... It just means:
17 > NEW will become CONFIRMED, NEW has been fully replaced by CONFIRMED so
18 > NEW is gone but CONFIRMED is *not* the new default status. CONFIRMED
19 > would/could be the default for everybody with editbugs.
20 > ASSIGNED gone, replacement: IN_PROGRESS,
21 > REOPENED gone,
22 > CLOSED gone. VERIFIED will be added.
23 >
24 > So I think we should convert...
25 >
26
27 I think I'll convert the workflow in about 24h if nobody really
28 complains. There is more positive feedback anyway.
29
30 --
31 Regards,
32 Christian Ruppert
33 Role: Gentoo Linux developer, Bugzilla administrator and Infrastructure
34 member
35 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>