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 1Pxdlm-0007A4-K4 for garchives@archives.gentoo.org; Thu, 10 Mar 2011 11:11:02 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4C5FA1C075; Thu, 10 Mar 2011 11:10:54 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id AEF6B1C074 for ; Thu, 10 Mar 2011 11:10:18 +0000 (UTC) Received: from [10.20.5.240] (fw-gw-atm.mimuw.edu.pl [193.0.96.15]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: phajdan.jr) by smtp.gentoo.org (Postfix) with ESMTPSA id DAAC91B4023 for ; Thu, 10 Mar 2011 11:10:17 +0000 (UTC) Message-ID: <4D78B196.80609@gentoo.org> Date: Thu, 10 Mar 2011 12:10:14 +0100 From: =?UTF-8?B?IlBhd2XFgiBIYWpkYW4sIEpyLiI=?= User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Bugzilla - New Default Status Workflow References: <4D737C71.1040806@gentoo.org> <20110306125029.GA9616@hrair> <4D74883E.9010004@gentoo.org> <20110307101352.GD9616@hrair> In-Reply-To: <20110307101352.GD9616@hrair> X-Enigmail-Version: 1.1.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8AAC3DFAB668268D98D32E83" X-Archives-Salt: X-Archives-Hash: 608d06d0470809abe714c16029b78552 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8AAC3DFAB668268D98D32E83 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 3/7/11 11:13 AM, Brian Harring wrote: > Re-read what he stated- it'll convert all existing NEW bugs to=20 > CONFIRMED upon migration. There's a fair number of bugs that are in a = > NEW state, decent number that have sat for a long while too. Those=20 > bugs aren't 'confirmed'- just like with the new work flow where the=20 > dev flips it from UNCONFIRMED to CONFIRMED, leave it to devs to flip=20 > the current bugs from UNCONFIRMED to CONFIRMED rather than just=20 > marking everything as CONFIRMED. Maybe I'm misunderstanding something, but it seems we have both UNCONFIRMED and NEW in the "old" workflow. My understanding is that CONFIRMED is the new name for NEW, which makes sense. --------------enig8AAC3DFAB668268D98D32E83 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAk14sZYACgkQuUQtlDBCeQK+DgCdEU/3ccQI5RL/OZpr78yhgFEj t14AnjO9I8piBWH1CntYwMcY4XYglgdF =jMRH -----END PGP SIGNATURE----- --------------enig8AAC3DFAB668268D98D32E83--