From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HdtGq-0005c5-3U for garchives@archives.gentoo.org; Tue, 17 Apr 2007 19:23:20 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l3HJMODK003653; Tue, 17 Apr 2007 19:22:24 GMT Received: from homeless.linbsd.net (homeless.linbsd.net [64.127.112.66]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l3HJJsVJ032727 for ; Tue, 17 Apr 2007 19:19:55 GMT Received: from [66.92.11.131] (dsl092-011-131.sfo1.dsl.speakeasy.net [66.92.11.131]) by homeless.linbsd.net (Postfix) with ESMTP id 6880A57D98 for ; Tue, 17 Apr 2007 12:19:54 -0700 (PDT) Subject: Re: [gentoo-dev] [POLICY] Keywording/Stabilizing Bug Assignment Policy From: Ned Ludd To: gentoo-dev@lists.gentoo.org In-Reply-To: <4625187A.4060403@gentoo.org> References: <4625187A.4060403@gentoo.org> Content-Type: text/plain Date: Tue, 17 Apr 2007 12:19:53 -0700 Message-Id: <1176837593.5462.12.camel@localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 4f2c6378-a178-4d6e-b86a-41a74929262a X-Archives-Hash: 5f72557ec9be1dcaf2823afdba067a35 On Tue, 2007-04-17 at 14:56 -0400, Doug Goldstein wrote: > I would like to take this time to note and re-affirm the proper bug > assignment policy and have it noted somewhere officially in Gentoo Policy. > > Bugs that are created for the purpose of getting arches to keyword or > stabilize a particular package should initially be assigned to the > herd/maintainer of said package with all requested arches being CCed. > Once all but the last arch has keyworded said package, it is acceptable > and proper for a bug wrangler and/or maintainer/herd to re-assign the > bug to the last remaining arch and they remove that arch from CC. They > should add their herd/maintainer to the CC of the bug. > > Once the last remaining arch has completed the bug, it is up to them to > close it. They know it's up to them to close it since the bug is > assigned directly to them. > > This helps keep bugzilla tidy and makes it easy to identify > stabilization/keywording requests which are a priority for that arch to > take care of. This is in direct conflict with the security bug policy handling which end up putting the maintainer on the CC: along with the arches. Also please don't cross post. -solar -- gentoo-dev@gentoo.org mailing list