public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Handling of keywording bugs with only one arch
Date: Sat, 27 Mar 2010 16:51:41 +0000	[thread overview]
Message-ID: <b41005391003270951g2f7354f4u2ccd3118bd2e497b@mail.gmail.com> (raw)
In-Reply-To: <20100327171641.TAdd9e4.tv@veller.net>

On Sat, Mar 27, 2010 at 4:45 PM, Torsten Veller <ml-en@veller.net> wrote:
> * Petteri Räty <betelgeuse@gentoo.org>:
>> So let's summarize for assigning to the single arch:
>
>> In support (and my comments in support):
>>  - Can be used as a gentle reminder for slacker arches
>
> And if not "only one arch" or "single arch" is slacking?
> I guess you would find another gentle way to remind them.
>
>
> How about a tool generating mails to arch teams, which lists all
> STABLEREQ, KEQWORDREQ bugs to which the arch team is CC'ed for a month?
> (Or probably easier or possible at all: which weren't changed for 30 days.)

I'd opt for a webpage personally.  I have found that push-nag systems
work well at first until the nagging increases to a level where the
nag-ee just filters the mail away.  This happens often at work.  For
example I get emails telling me to delete unused perforce clients; but
those mails just get marked as read by a filter and archived.

Could we generate a bugzilla search for arch teams?  Do arch teams
already use existing bugzilla functionality?

-A

>
>



  reply	other threads:[~2010-03-27 16:51 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 [this message]
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=b41005391003270951g2f7354f4u2ccd3118bd2e497b@mail.gmail.com \
    --to=antarus@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