From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PxtPa-0008QR-IH for garchives@archives.gentoo.org; Fri, 11 Mar 2011 03:53:12 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2218CE0603; Fri, 11 Mar 2011 03:52:58 +0000 (UTC) Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by pigeon.gentoo.org (Postfix) with ESMTP id 8A4A3E05CF for ; Fri, 11 Mar 2011 03:52:21 +0000 (UTC) Received: from epia.jer-c2.orkz.net (D4B2706A.static.ziggozakelijk.nl [212.178.112.106]) (authenticated bits=0) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id p2B3qKn8098455 for ; Fri, 11 Mar 2011 04:52:20 +0100 (CET) (envelope-from jer@gentoo.org) Date: Fri, 11 Mar 2011 04:52:19 +0100 From: Jeroen Roovers To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Bugzilla - New Default Status Workflow Message-ID: <20110311045219.032437fe@epia.jer-c2.orkz.net> In-Reply-To: <1299786777-sup-5793@ittemni> References: <4D737C71.1040806@gentoo.org> <20110306125029.GA9616@hrair> <4D74883E.9010004@gentoo.org> <20110307101352.GD9616@hrair> <4D78B196.80609@gentoo.org> <20110310111542.GA10933@Eternity.halls.manchester.ac.uk> <20110310204229.314f784d@epia.jer-c2.orkz.net> <1299786777-sup-5793@ittemni> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.20.1; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by XS4ALL Virus Scanner X-Archives-Salt: X-Archives-Hash: 4fc9c010ed1664c4ab2ccacfe1e6359f On Thu, 10 Mar 2011 21:06:54 +0100 Amadeusz =C5=BBo=C5=82nowski wrote: > > Status =3D NEW && Assignee =3D bug-wranglers -> Status =3D UNCONFIRMED > > Status =3D NEW && Assignee =3D [maintainer] -> Status =3D CONFIRMED >=20 > Who confirms the bug? I would expect that CONFIRMED is set by the > package maintainer and the one who assigns bugs leaves the status. I was referring to existing bug reports, not new ones. New ones should come in as UNCONFIRMED and would be changed to CONFIRMED when assigned - bug wrangling does have this element of validation, you know. Apparently when maintainers accept the bug, it changes to IN PROGRESS, and when [s]he doesn't it should be resolved as invalid or duplicate or whatever, but heck, maybe the flow chart should speak for itself. Here is the URL again: http://www.bugzilla.org/docs/4.0/en/html/lifecycle.html jer