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 1PwVvn-0002yX-Cf for garchives@archives.gentoo.org; Mon, 07 Mar 2011 08:36:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3F6021C029; Mon, 7 Mar 2011 08:36:31 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id E25ED1C007 for ; Mon, 7 Mar 2011 08:35:55 +0000 (UTC) Received: from pomiocik.lan (77-254-77-36.adsl.inetia.pl [77.254.77.36]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 2BD251B40A6; Mon, 7 Mar 2011 08:35:53 +0000 (UTC) Date: Mon, 7 Mar 2011 09:34:55 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: idl0r@gentoo.org Subject: Re: [gentoo-dev] Bugzilla - New Default Status Workflow Message-ID: <20110307093455.0060e0c9@pomiocik.lan> In-Reply-To: <4D737C71.1040806@gentoo.org> References: <4D737C71.1040806@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.7.8 (GTK+ 2.24.1; x86_64-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: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/RNTt+UT=eyicaGpaRXmvlYK"; protocol="application/pgp-signature" X-Archives-Salt: X-Archives-Hash: 33e6f39fbfafe95c18c563b12c61d9f0 --Sig_/RNTt+UT=eyicaGpaRXmvlYK Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, 06 Mar 2011 13:22:09 +0100 Christian Ruppert 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. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/RNTt+UT=eyicaGpaRXmvlYK Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk10mLUACgkQnGSe5QXeB7uFygCfSFcenLnksTqMwvoSetoAwroI cswAoJPAnLZ9VUrIrF63qUEbZsX1MfAE =/Rzh -----END PGP SIGNATURE----- --Sig_/RNTt+UT=eyicaGpaRXmvlYK--