From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] reminding slacker arch's to handle bugs
Date: Sat, 27 Mar 2010 15:58:41 -0500 [thread overview]
Message-ID: <20100327205841.GA12996@linux1> (raw)
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
On Sat, Mar 27, 2010 at 05:45:51PM +0100, Torsten Veller 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 know that I have several bugs right now with minor arch's on them
waiting to be stabilized. A couple have been waiting for a very long
time. I have even pinged some of the bugs several times with no response.
Is there anything else I can do to get these arch teams attention?
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-03-27 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 20:58 William Hubbs [this message]
2010-03-28 5:47 ` [gentoo-dev] [RFC] Reworking package stabilization policies Maciej Mrozowski
2010-03-28 6:31 ` Alistair Bush
2010-03-28 6:34 ` Brian Harring
2010-03-28 6:56 ` Alistair Bush
2010-03-28 9:43 ` [gentoo-dev] " Duncan
2010-03-28 20:35 ` [gentoo-dev] " William Hubbs
2010-03-28 7:39 ` Ciaran McCreesh
2010-03-28 10:04 ` Tomáš Chvátal
2010-03-28 11:32 ` Richard Freeman
2010-03-28 15:18 ` Maciej Mrozowski
2010-03-29 7:30 ` Peter Volkov
2010-03-29 17:10 ` Maciej Mrozowski
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=20100327205841.GA12996@linux1 \
--to=williamh@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