On Tuesday 17 April 2007 21:36, Doug Goldstein wrote: > Ned Ludd wrote: > > 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 > > Then can we officially say this is at the discretion of the maintainer > of said package then? Security bugs are assigned to security for all their lifetime and we handle all bug wrangling. But if that is the only exception a simple note should suffice.
-- Sune Kloppenborg Jeppesen Gentoo Linux Security Team
pgpTdcUYMZPo3.pgp
Description: PGP signature
