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
On 04/30/2011 10:40 AM, Christian Ruppert wrote:
> On 04/28/2011 04:07 PM, Christian Ruppert wrote: >> So once again: >> >> https://bugs.gentoo.org/docs/en/html/lifecycle.html >> >> *Every* new bug filed by a user without editbugs will have "UNCONFIRMED" >> (old NEW) as fixed status. >> *If* we don't enable the UNCONFIRMED status at all then it will >> CONFIRMED as default but we would enable the UNCONFIRMED status. >> >> Bug wranglers can then assign the bug and they also *can* mark it as >> CONFIRMED *if* they *can* confirm it. >> The maintainer may change the status to IN_PROGRESS (old ASSIGNED) >> afterwards. >> >> The snipped of my first mail may be a bit confusing... It just means: >> NEW will become CONFIRMED, NEW has been fully replaced by CONFIRMED so >> NEW is gone but CONFIRMED is *not* the new default status. CONFIRMED >> would/could be the default for everybody with editbugs. >> ASSIGNED gone, replacement: IN_PROGRESS, >> REOPENED gone, >> CLOSED gone. VERIFIED will be added. >> >> So I think we should convert... >> > > I think I'll convert the workflow in about 24h if nobody really > complains. There is more positive feedback anyway. >
Done. The new workflow is online. -- Regards, Christian Ruppert Role: Gentoo Linux developer, Bugzilla administrator and Infrastructure member 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>