Gentoo Archives: gentoo-dev

From: "Amadeusz Żołnowski" <aidecoe@g.o>
To: gentoo-dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] Bugzilla - New Default Status Workflow
Date: Thu, 10 Mar 2011 20:07:47
Message-Id: 1299786777-sup-5793@ittemni
In Reply to: Re: [gentoo-dev] Bugzilla - New Default Status Workflow by Jeroen Roovers
1 Excerpts from Jeroen Roovers's message of Thu Mar 10 20:42:29 +0100 2011:
2 > For existing bugs, then, NEW bugs should be changed to UNCONFIRMED
3 > when they are assigned to bug-wranglers, and to CONFIRMED when they
4 > have already been assigned to their maintainers (irrespective of
5 > whether they are actually confirmed or not or whether they are deemed
6 > to be actual bugs).
7 >
8 > Status = NEW && Assignee = bug-wranglers -> Status = UNCONFIRMED
9 > Status = NEW && Assignee = [maintainer] -> Status = CONFIRMED
10
11 Who confirms the bug? I would expect that CONFIRMED is set by the
12 package maintainer and the one who assigns bugs leaves the status.
13 --
14 Amadeusz Żołnowski
15
16 PGP key fpr: C700 CEDE 0C18 212E 49DA 4653 F013 4531 E1DB FAB5

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] Bugzilla - New Default Status Workflow Jeroen Roovers <jer@g.o>