List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Thu, Apr 28, 2011 at 04:07:24PM +0200, Christian Ruppert wrote:
> So once again:
> *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)
> 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...
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.
> Christian Ruppert
> Role: Gentoo Linux developer, Bugzilla administrator and Infrastructure
> Fingerprint: EEB1 C341 7C84 B274 6C59 F243 5EAB 0C62 B427 ABC8
Alex Alexander | wired
+ Gentoo Linux Developer