Gentoo Archives: gentoo-dev

From: Brian Harring <ferringb@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Bugzilla - New Default Status Workflow
Date: Sun, 06 Mar 2011 12:51:38
Message-Id: 20110306125029.GA9616@hrair
In Reply to: [gentoo-dev] Bugzilla - New Default Status Workflow by Christian Ruppert
On Sun, Mar 06, 2011 at 01:22:09PM +0100, Christian Ruppert wrote:
> Hey guys, > > in bugzilla-4.x they did change the "Status Workflow"[1]. > > <snip> > This will convert the status of all bugs using the following > system: > > "NEW" will become "CONFIRMED"
This seems mildly insane; sure you didn't mean UNCONFIRMED?
> "ASSIGNED" will become "IN_PROGRESS" > "REOPENED" will become "CONFIRMED" (and the "REOPENED" status will be > removed)
Similarly weird.
> "CLOSED" will become "VERIFIED" (and the "CLOSED" status will be removed)
VERIFIED != CLOSED; CLOSED means "this issue should be fixed", VERIFIED means "this issue is confirmed fixed by whatever qa/testing in use"- specifically beyond the developer's testing.
> We're almost done with the preparation of bugzilla-4.x for > So, do we want the new workflow or do we want to keep the old?
The new is more orientated towards bugzilla workflow's that have actual secondary validation of a change- developer fixes it, closes it, QA marks it verified, that sort of thing. That doesn't really fit our flow all that much, as such we really shouldn't be taking their defaults without tweaking it a bit. ~brian