From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keyword request interface (SoC candidate?)
Date: Fri, 29 Feb 2008 18:26:52 -0500 [thread overview]
Message-ID: <47C894BC.4050200@gentoo.org> (raw)
In-Reply-To: <97a7f0880802291127w283962f3jb4c497f36fcf9649@mail.gmail.com>
Aaron Mavrinac wrote:
>
> This would certainly help coordinate AT efforts. Couldn't this also be
> done by searching through bugzilla? Maybe with an "official" keyword,
> or some sort of flag we don't otherwise use? (I'm not intensely
> familiar with bugzilla internals.) Keeping it all in bugzilla seems
> best, if possible.
I know that the amd64 team used to use the "STABLE" and "TESTED"
keywords to indicate that an AT felt it was ok to keyword stable or
~arch respectively. I guess that practice went away. It doesn't work
so well on bugs with 5 archs CC'ed though. Maybe we need STABLEAMD64,
STABLEX86, etc.
As an AT I used to run queries all the time looking for bugs that
weren't keyworded STABLE/TESTED and which otherwise looked like they
needed AT attention. I still check the corresponding developer query
for stuff keyworded STABLE/TESTED with amd64 CC'ed...
There are definitely some easy ways to improve things that don't require
code changes...
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-29 23:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 17:33 [gentoo-dev] Keyword request interface (SoC candidate?) Santiago M. Mola
2008-02-28 17:50 ` Torsten Rehn
2008-02-28 21:43 ` Alec Warner
2008-02-28 21:47 ` Santiago M. Mola
2008-02-29 2:49 ` Richard Freeman
2008-02-29 9:44 ` Peter Volkov
2008-02-29 11:11 ` Rémi Cardona
2008-02-29 18:13 ` Richard Freeman
2008-02-29 18:29 ` Thomas Anderson
2008-02-29 19:27 ` Aaron Mavrinac
2008-02-29 23:26 ` Richard Freeman [this message]
2008-02-29 23:48 ` Aaron Mavrinac
2008-02-29 23:20 ` [OT] " Andrej Kacian
2008-02-29 20:37 ` Bernd Steinhauser
2008-03-01 15:24 ` [gentoo-dev] " 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=47C894BC.4050200@gentoo.org \
--to=rich0@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