public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [POLICY] Keywording/Stabilizing Bug Assignment Policy
Date: Tue, 17 Apr 2007 12:19:53 -0700	[thread overview]
Message-ID: <1176837593.5462.12.camel@localhost> (raw)
In-Reply-To: <4625187A.4060403@gentoo.org>

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



  parent reply	other threads:[~2007-04-17 19:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 18:56 [gentoo-dev] [POLICY] Keywording/Stabilizing Bug Assignment Policy Doug Goldstein
2007-04-17 19:17 ` Ciaran McCreesh
2007-04-17 19:19 ` Ned Ludd [this message]
2007-04-17 19:36   ` Doug Goldstein
2007-04-17 19:57     ` Sune Kloppenborg Jeppesen
2007-04-17 19:50 ` [gentoo-dev] Re: [gentoo-core] " Stefan Schweizer
2007-04-17 20:06   ` Bryan Østergaard
2007-04-17 20:06   ` [gentoo-dev] " Alin Năstac
2007-04-17 20:25   ` [gentoo-dev] Re: [gentoo-core] " Chris Gianelloni
2007-04-17 22:36   ` Vlastimil Babka
2007-04-18 13:39     ` Jim Ramsay
2007-04-18 13:57       ` Chris Gianelloni
2007-04-18 15:14         ` Jim Ramsay
2007-05-27 10:23           ` [gentoo-dev] STABLEREQ/KEYWORDREQ Keywords in bugzilla Vlastimil Babka
2007-05-27 10:39             ` Robin H. Johnson
2007-05-27 11:06               ` Vlastimil Babka
2007-04-17 20:07 ` [gentoo-dev] [POLICY] Keywording/Stabilizing Bug Assignment Policy Samuli Suominen
2007-04-18 13:59 ` Mart Raudsepp
2007-04-20 23:33 ` [gentoo-dev] " Ryan Hill
2007-04-21  2:55   ` Chris Gianelloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1176837593.5462.12.camel@localhost \
    --to=solar@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox