| 1 |
On Sat, Mar 27, 2010 at 4:45 PM, Torsten Veller <ml-en@××××××.net> wrote: |
| 2 |
> * Petteri Räty <betelgeuse@g.o>: |
| 3 |
>> So let's summarize for assigning to the single arch: |
| 4 |
> |
| 5 |
>> In support (and my comments in support): |
| 6 |
>> - Can be used as a gentle reminder for slacker arches |
| 7 |
> |
| 8 |
> And if not "only one arch" or "single arch" is slacking? |
| 9 |
> I guess you would find another gentle way to remind them. |
| 10 |
> |
| 11 |
> |
| 12 |
> How about a tool generating mails to arch teams, which lists all |
| 13 |
> STABLEREQ, KEQWORDREQ bugs to which the arch team is CC'ed for a month? |
| 14 |
> (Or probably easier or possible at all: which weren't changed for 30 days.) |
| 15 |
|
| 16 |
I'd opt for a webpage personally. I have found that push-nag systems |
| 17 |
work well at first until the nagging increases to a level where the |
| 18 |
nag-ee just filters the mail away. This happens often at work. For |
| 19 |
example I get emails telling me to delete unused perforce clients; but |
| 20 |
those mails just get marked as read by a filter and archived. |
| 21 |
|
| 22 |
Could we generate a bugzilla search for arch teams? Do arch teams |
| 23 |
already use existing bugzilla functionality? |
| 24 |
|
| 25 |
-A |
| 26 |
|
| 27 |
> |
| 28 |
> |
Archives