public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] changes to tested bugzilla keyword proposal
Date: Wed, 9 Jan 2013 14:49:09 -0500	[thread overview]
Message-ID: <CAGfcS_=88q6xmXxFpFmFtYu4i+e+7VK5u9cFhdm6XsrVEP=Osw@mail.gmail.com> (raw)
In-Reply-To: <20130109180201.57b56cb2@marga.jer-c2.orkz.net>

On Wed, Jan 9, 2013 at 12:02 PM, Jeroen Roovers <jer@gentoo.org> wrote:
> A lot clearer than a single text field littered with keywords would be some
> tick boxes, indeed. In fact, it makes me wonder why we use a half-obscured list
> in a select field for adding/removing arch teams now.

Agree - mostly legacy (perhaps due to previous limitations in bugzilla?).

Non-arch-specific tested/stable keywords are useless IMHO.  Their main
purpose is for bug filtering.  The concept is that you have a large
team of arch testers who can do the testing, and a smaller team of
devs with commit access who search for bugs with the appropriate marks
and do the commit/close (often with little testing of their own).

When only amd64 was doing it the single keyword worked fine.

Do we have enough ATs around that this is even worth having any
longer?  I know that whenever I run my keyworded-but-still-amd64-cc
query it is pretty rare for stuff to come up.  Years ago that was the
arch team bread-and-butter.

Rich


  reply	other threads:[~2013-01-09 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 16:17 [gentoo-dev] changes to tested bugzilla keyword proposal Vicente Olivert Riera
2013-01-09 16:39 ` Markos Chandras
2013-01-09 17:02   ` Jeroen Roovers
2013-01-09 19:49     ` Rich Freeman [this message]
2013-02-01  5:37     ` [gentoo-dev] " Ryan Hill
2013-02-01 11:15       ` Rich Freeman
2013-02-03  7:41         ` Ryan Hill
2013-02-03  8:21           ` 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='CAGfcS_=88q6xmXxFpFmFtYu4i+e+7VK5u9cFhdm6XsrVEP=Osw@mail.gmail.com' \
    --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