From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Handling of keywording bugs with only one arch
Date: Sat, 13 Mar 2010 19:07:41 +0200 [thread overview]
Message-ID: <4B9BC65D.9000504@gentoo.org> (raw)
In-Reply-To: <e8a2d32ba4bc39ee8c0d7eb43092bede@jolexa.net>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
On 03/12/2010 10:11 PM, Jeremy Olexa wrote:
>
> On Fri, 12 Mar 2010 21:18:03 +0200, Petteri Räty <betelgeuse@gentoo.org>
> 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.
>
> The "problem" with assigning bugs to arch teams is when the user comments
> on the bug after it is resolved. If the arch team is CC'd, they remove
> themselves when done and any comments after the bug is closed goes to
> someone that is interested. If the arch team is assigned, then the comment
> basically goes to /dev/null. So, if we are to improve the user experience,
> assign to maintainer and CC arch team.
>
> -Jeremy
>
When a bug is marked as fixed it doesn't show up in searches developers
use so it's a matter of who reads the email and acts upon it. I don't
see why maintainers would be any more likely to act than an arch team
comprised of multiple people in the case of bigger arches. Let's not
forget that users are really supposed to open new bugs instead of
commenting on the resolved ones although I know there are users out
there who rather comment on a two year old only distantly related bug
than open a new one.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2010-03-13 17:08 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 [this message]
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
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=4B9BC65D.9000504@gentoo.org \
--to=betelgeuse@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