Gentoo Archives: gentoo-dev

From: Jeroen Roovers <jer@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Bugzilla - New Default Status Workflow
Date: Fri, 11 Mar 2011 03:53:12
Message-Id: 20110311045219.032437fe@epia.jer-c2.orkz.net
In Reply to: Re: [gentoo-dev] Bugzilla - New Default Status Workflow by "Amadeusz Żołnowski"
1 On Thu, 10 Mar 2011 21:06:54 +0100
2 Amadeusz Żołnowski <aidecoe@g.o> wrote:
3
4 > > Status = NEW && Assignee = bug-wranglers -> Status = UNCONFIRMED
5 > > Status = NEW && Assignee = [maintainer] -> Status = CONFIRMED
6 >
7 > Who confirms the bug? I would expect that CONFIRMED is set by the
8 > package maintainer and the one who assigns bugs leaves the status.
9
10 I was referring to existing bug reports, not new ones. New ones should
11 come in as UNCONFIRMED and would be changed to CONFIRMED when assigned
12 - bug wrangling does have this element of validation, you know.
13 Apparently when maintainers accept the bug, it changes to IN PROGRESS,
14 and when [s]he doesn't it should be resolved as invalid or duplicate
15 or whatever, but heck, maybe the flow chart should speak for itself.
16
17 Here is the URL again:
18
19 http://www.bugzilla.org/docs/4.0/en/html/lifecycle.html
20
21
22 jer

Replies

Subject Author
[gentoo-dev] Re: Bugzilla - New Default Status Workflow Ryan Hill <dirtyepic@g.o>