Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Michał Górny <mgorny@g.o>
Subject: Re: Bugzilla - New Default Status Workflow
Date: Mon, 7 Mar 2011 09:34:55 +0100
On Sun, 06 Mar 2011 13:22:09 +0100
Christian Ruppert <idl0r@g.o> wrote:

>   "NEW" will become "CONFIRMED"
>   "REOPENED" will become "CONFIRMED" (and the "REOPENED" status will
> be removed)

I'd say, both to UNCONFIRMED. Before, we used to set 'NEW' for newly-
added bugs and didn't use UNCONFIRMED often. Right now, it seems
logical to use UNCONFIRMED for the new bugs and let devs (re-)confirm
them as necessary.

I think it might be even a good idea to limit the possibility
of setting 'CONFIRMED' to devs. Otherwise, I see users bumping each
of their bugs to 'CONFIRMED' immediately.

> We're almost done with the preparation of bugzilla-4.x for
> bugs.gentoo.org. So, do we want the new workflow or do we want to
> keep the old?

New one. Simpler is better.

-- 
Best regards,
Michał Górny
Attachment:
signature.asc (PGP signature)
Replies:
Re: Bugzilla - New Default Status Workflow
-- Duncan
References:
Bugzilla - New Default Status Workflow
-- Christian Ruppert
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Bugzilla - New Default Status Workflow
Next by thread:
Re: Bugzilla - New Default Status Workflow
Previous by date:
Re: Bugzilla - New Default Status Workflow
Next by date:
Re: Bugzilla 4 migration


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.