On Sat, Mar 27, 2010 at 4:45 PM, Torsten Veller <ml...@veller.net> wrote:
> * Petteri Räty <betelge...@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 via email to