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 <gentoo-dev+bounces-44781-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1PxiMP-00079a-56
for garchives@archives.gentoo.org; Thu, 10 Mar 2011 16:05:09 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 356021C00A;
Thu, 10 Mar 2011 16:04:57 +0000 (UTC)
Received: from mail-pw0-f53.google.com (mail-pw0-f53.google.com [209.85.160.53])
by pigeon.gentoo.org (Postfix) with ESMTP id 0D3E3E0691
for <gentoo-dev@lists.gentoo.org>; Thu, 10 Mar 2011 16:04:20 +0000 (UTC)
Received: by pwj7 with SMTP id 7so706818pwj.40
for <gentoo-dev@lists.gentoo.org>; Thu, 10 Mar 2011 08:04:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:in-reply-to:references:date
:message-id:subject:from:to:content-type:content-transfer-encoding;
bh=l4R+0fF2FpRfFBqJL6NZytKwYWTzSHpK/sF/xf7yBCo=;
b=xdEFfe+X+bQgHiNMaYoJ0gGtMpgMzS3MS6LdeLEKonNz5PhiyoPGRV0kHMlMdfPHe0
dZc26nIvjzbp2V8uW1EAkn8Hfwo7f6kxKmAEOtkL48fQ102RxNq5XUCbkXINd+AoxdAm
mlWqT/m4z4XxpIFMIxHvNJNnbUHNMemZgLoC4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type:content-transfer-encoding;
b=YvpXDWJSSU0hBrTzjmCCyPbMJhnhtce+mvUJxQsulz5n9W5F0UX9ig5BEeaaKxY8H3
QDwnYKJtWRDnWnGvvOsS09VgTGH1BEBNbVc8XUX6YYe7ldTjf2oPZn9ns9Ijfy+0OEub
hPcmKUKaLXqb2WOpjAWnCEY8IibZhNT2W0T9w=
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.142.8.30 with SMTP id 30mr6725189wfh.235.1299773059949; Thu,
10 Mar 2011 08:04:19 -0800 (PST)
Received: by 10.142.136.7 with HTTP; Thu, 10 Mar 2011 08:04:19 -0800 (PST)
In-Reply-To: <20110310111542.GA10933@Eternity.halls.manchester.ac.uk>
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>
Date: Thu, 10 Mar 2011 11:04:19 -0500
Message-ID: <AANLkTi=6ta1QFv=fjpM_Hb49LrdYbc4KEjZ3vf2MOgU7@mail.gmail.com>
Subject: Re: [gentoo-dev] Bugzilla - New Default Status Workflow
From: Mike Gilbert <floppymaster@gmail.com>
To: gentoo-dev@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt:
X-Archives-Hash: 25a42771e329f99ebd72cfab32906e93
On Thu, Mar 10, 2011 at 6:15 AM, Markos Chandras <hwoarang@gentoo.org> wrot=
e:
> On Thu, Mar 10, 2011 at 12:10:14PM +0100, "Pawe=C5=82 Hajdan, Jr." wrote:
>> On 3/7/11 11:13 AM, Brian Harring wrote:
>> > Re-read what he stated- it'll convert all existing NEW bugs to
>> > CONFIRMED upon migration. =C2=A0There's a fair number of bugs that are=
in a
>> > NEW state, decent number that have sat for a long while too. =C2=A0Tho=
se
>> > bugs aren't 'confirmed'- just like with the new work flow where the
>> > dev flips it from UNCONFIRMED to CONFIRMED, leave it to devs to flip
>> > the current bugs from UNCONFIRMED to CONFIRMED rather than just
>> > 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.
>>
> Sorry but no. NEW means "Ok I think this is a bug. Can you please take a
> look?". CONFIRMED is "ok this is definitely a bug. I am able to
> reproduce etc and will look into fixing it". The meaning is slightly
> different but it is important to distinguish valid from invalid bugs.
>
>
> Regards,
> --
> Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
>
If we were to switch to the new workflow, it probably would make sense
to switch the default new bug status to UNCONFIRMED. I'm not sure how
we would handle the existing bugs in NEW status.
Here are the workflow diagrams for our old Bugzilla and the new one. I
find pictures are a bit easier to follow.
Bugzilla 2.22:
http://www.bugzilla.org/docs/2.22/html/lifecycle.html
Bugzilla 4.0:
http://www.bugzilla.org/docs/4.0/en/html/lifecycle.html