Gentoo Archives: gentoo-dev

From: Alex Alexander <wired@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Bugzilla - New Default Status Workflow
Date: Thu, 28 Apr 2011 15:11:27
Message-Id: 20110428150707.GA8190@linuxized.com
In Reply to: Re: [gentoo-dev] Bugzilla - New Default Status Workflow by Christian Ruppert
On Thu, Apr 28, 2011 at 04:07:24PM +0200, 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...
+1 The new workflow makes more sense. I would mark any new bug as UNCONFIRMED by default, having editbugs doesn't ensure your bugs will be confirmed.
> -- > Regards, > Christian Ruppert > Role: Gentoo Linux developer, Bugzilla administrator and Infrastructure > member > Fingerprint: EEB1 C341 7C84 B274 6C59 F243 5EAB 0C62 B427 ABC8
-- Alex Alexander | wired + Gentoo Linux Developer ++ www.linuxized.com