From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Handling of keywording bugs with only one arch
Date: Sat, 10 Apr 2010 16:38:46 -0600 [thread overview]
Message-ID: <20100410163846.782e121c@gentoo.org> (raw)
In-Reply-To: 4BAE15A6.80101@gentoo.org
[-- Attachment #1: Type: text/plain, Size: 2161 bytes --]
On Sat, 27 Mar 2010 16:26:46 +0200
Petteri Räty <betelgeuse@gentoo.org> wrote:
> On 03/12/2010 09:18 PM, Petteri Räty wrote:
> > There seems to be two different schools on who to assign a keywording
> > bug with only a single arch. I have myself assigned it to the arch in
> > question but there's a difference of opinion here:
> > http://bugs.gentoo.org/show_bug.cgi?id=272160#c5
> > Let's get agreed on a single approach and I will add a note here:
> > http://devmanual.gentoo.org/keywording/index.html
> > I naturally support the approach I have been doing as I think the arch
> > team is the one in charge.
> >
> > Regards,
> > Petteri
> >
>
> So let's summarize for assigning to the single arch:
>
> Against (and my comments on why they don't apply):
> - Comments would only go to arch team after resolving:
> * maintainer is still in Cc or Reporter
> - Arch teams not in charge of fixing problems
> * If problems come up they deserve a new bug as a dependency
> * one bug per issue and a stabilization bug is about stabilization
> - Maintainer being able to decide when to go stable
> * Bug wranglers should still assign to maintainers for their ack
> * The maintainer assigns it to the arch team
>
> In support (and my comments in support):
> - Can be used as a gentle reminder for slacker arches
> - The arch teams are actually ones doing the work to resolve the bug
> * As they are the ones to mark it as resolved it makes sense for them
> to be the assignees
>
> So based on this I propose that I will write this down in appropriate
> places in to our documentation and commit a week from now. Please object
> if you don't agree and we can discuss some more.
You ignored my point about this being completely moot once we start using
flags in bugzilla for arch teams. We'll have to change the policy then
to the maintainer being the assignee anyways.
--
fonts, by design, by neglect
gcc-porting, for a fact or just for effect
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-04-10 22:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 19:18 [gentoo-dev] Handling of keywording bugs with only one arch Petteri Räty
2010-03-12 19:39 ` "Paweł Hajdan, Jr."
2010-03-12 19:55 ` Petteri Räty
2010-03-12 19:54 ` Samuli Suominen
2010-03-12 20:11 ` Jeremy Olexa
2010-03-12 21:47 ` William Hubbs
2010-03-12 22:58 ` Jorge Manuel B. S. Vicetto
2010-03-13 11:08 ` Markos Chandras
2010-03-13 17:09 ` Petteri Räty
2010-03-13 17:07 ` Petteri Räty
2010-03-13 17:21 ` Samuli Suominen
2010-03-13 17:27 ` Petteri Räty
2010-03-13 22:43 ` [gentoo-dev] " Duncan
2010-03-14 8:56 ` Ryan Hill
2010-03-14 9:21 ` Petteri Räty
2010-03-14 23:41 ` Ryan Hill
2010-03-12 23:03 ` Ryan Hill
2010-03-12 23:17 ` Matti Bickel
2010-03-14 16:38 ` [gentoo-dev] " Thomas Sachau
2010-03-27 14:26 ` Petteri Räty
2010-03-27 14:51 ` Alex Alexander
2010-03-27 15:07 ` Petteri Räty
2010-04-01 20:28 ` Jeroen Roovers
2010-04-04 9:38 ` Petteri Räty
2010-03-27 16:45 ` [gentoo-dev] " Torsten Veller
2010-03-27 16:51 ` Alec Warner
2010-03-27 17:20 ` Matti Bickel
2010-04-10 22:38 ` Ryan Hill [this message]
2010-04-10 22:41 ` Petteri Räty
2010-04-10 23:12 ` Ryan Hill
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=20100410163846.782e121c@gentoo.org \
--to=dirtyepic@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