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 1OsX86-0007DB-Bz for garchives@archives.gentoo.org; Mon, 06 Sep 2010 08:32:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 365F6E0783; Mon, 6 Sep 2010 08:32:37 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 309DEE074B for ; Mon, 6 Sep 2010 08:32:19 +0000 (UTC) Received: from mail.isohunt.com (b01.ext.isohunt.com [208.71.112.51]) by smtp.gentoo.org (Postfix) with ESMTP id 932C71B401E for ; Mon, 6 Sep 2010 08:32:18 +0000 (UTC) Received: (qmail 21250 invoked from network); 6 Sep 2010 08:32:18 -0000 Received: from tsi-static.orbis-terrarum.net (HELO grubbs.orbis-terrarum.net) (76.10.188.108) by mail.isohunt.com (qpsmtpd/0.33-dev on beta01) with (CAMELLIA256-SHA encrypted) ESMTPS; Mon, 06 Sep 2010 08:32:18 +0000 Received: (qmail 23963 invoked by uid 10000); 6 Sep 2010 08:32:16 -0000 Date: Mon, 6 Sep 2010 08:32:16 +0000 From: "Robin H. Johnson" To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users Message-ID: 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; protocol="application/pgp-signature"; boundary="E7i4zwmWs5DOuDSH" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Archives-Salt: 1870126e-9e1c-4811-932b-1281fe3ada6f X-Archives-Hash: e237525e105a47643d9699eb2545df90 --E7i4zwmWs5DOuDSH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, 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. These is the simplest set I have to start, but I'd really like other comments and ideas. 1. General case - You should only close bugs that you are assigned or if you (or an alias you represent) just fixed them. - If you fix a bug and AREN'T already getting mail for it, you should add yourself to the CC list, to listen for regressions or responses to TESTREQUEST. 2. Special cases 2.1. STABLEREQ, KEYWORDREQ The last arch on the list should close the bug when they have completed the action. 2.2. Security bugs The developer should comment, but ONLY members of the security team should: - change whiteboard - add/remove arches - change bug status/reso --=20 Robin Hugh Johnson Gentoo Linux: Developer, Trustee & Infrastructure Lead E-Mail : robbat2@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 --E7i4zwmWs5DOuDSH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Robbat2 @ Orbis-Terrarum Networks - The text below is a digital signature. If it doesn't make any sense to you, ignore it. iEYEARECAAYFAkyEpw8ACgkQPpIsIjIzwiyXyACfc1GEt7HrddAJbToN6gfVoD76 eIEAn123Ki4IL+ezhxUZJ2loMYPQIbKS =2wmW -----END PGP SIGNATURE----- --E7i4zwmWs5DOuDSH--