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 1OsXFp-00087S-2v for garchives@archives.gentoo.org; Mon, 06 Sep 2010 08:40:41 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A0D73E07A0; Mon, 6 Sep 2010 08:40:35 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id B1EBDE0595 for ; Mon, 6 Sep 2010 08:40:22 +0000 (UTC) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPSA id 128DB1B40B1 for ; Mon, 6 Sep 2010 08:40:21 +0000 (UTC) Received: by wyf28 with SMTP id 28so5205106wyf.40 for ; Mon, 06 Sep 2010 01:40:19 -0700 (PDT) Received: by 10.216.45.16 with SMTP id o16mr2481055web.45.1283762419120; Mon, 06 Sep 2010 01:40:19 -0700 (PDT) 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 Received: by 10.216.136.32 with HTTP; Mon, 6 Sep 2010 01:39:59 -0700 (PDT) In-Reply-To: References: From: Dirkjan Ochtman Date: Mon, 6 Sep 2010 10:39:59 +0200 Message-ID: Subject: Re: [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 6c04582a-6573-431b-8780-ab82ee65d409 X-Archives-Hash: d9169ec9a0133fbd80edab11ee95399c On Mon, Sep 6, 2010 at 10:32, Robin H. Johnson wrote: > After a discussion on IRC, a few of us were considering the value of > adding suggestions on handling of bugs in Bugzilla from a developer (and > editbugs user) perspective. Good idea, I've been confused about the interaction models here. > 1. General case > =C2=A0- You should only close bugs that you are assigned or if you (or an= alias > =C2=A0 =C2=A0 =C2=A0 =C2=A0you represent) just fixed them. > =C2=A0- If you fix a bug and AREN'T already getting mail for it, you shou= ld > =C2=A0 =C2=A0 =C2=A0 =C2=A0add yourself to the CC list, to listen for reg= ressions or responses > =C2=A0 =C2=A0 =C2=A0 =C2=A0to TESTREQUEST. Only add arches to stabilization requests if you're a maintainer? > 2. Special cases > 2.1. STABLEREQ, KEYWORDREQ > =C2=A0The last arch on the list should close the bug when they have compl= eted > =C2=A0the action. > > 2.2. Security bugs > =C2=A0The developer should comment, but ONLY members of the security team > =C2=A0should: > =C2=A0- change whiteboard > =C2=A0- add/remove arches > =C2=A0- change bug status/reso The arches can still remove themselves when they've done whatever they needed to do, right? Cheers, Dirkjan