[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] Keyword request interface (SoC candidate?)
From:       "Aaron Mavrinac" <mavrinac () gmail ! com>
Date:       2008-02-29 23:48:59
Message-ID: 97a7f0880802291548m506296b5seb3b72e426f52da2 () mail ! gmail ! com
[Download RAW message or body]

On Fri, Feb 29, 2008 at 6:26 PM, Richard Freeman <rich0@gentoo.org> wrote:
>  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.

Yes, that's exactly what I'm talking about. When I open a
stable/tested bug specifically for sparc, I use those keywords, but
like you said, that doesn't apply when the request hits multiple
archs.

>  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...

Some sort of front-end web app could be useful for the following:

1. Properly and consistently format user stable requests and AT/dev
responses for storage in bugzilla (and avoid dupes).
2. Provide pre-fabricated bugzilla queries (and relevant formatted
output) for common related AT/dev tasks.
3. Interface with packages.gentoo.org.
4. Provide at-your-fingertips cvs info, rdep info, open bugs, stable
requests for previous versions, gatt info, etc.

-- 
Aaron Mavrinac
www.mavrinac.com

PGP Public Key: http://www.mavrinac.com/pgp.asc
-- 
gentoo-dev@lists.gentoo.org mailing list

[prev in list] [next in list] [prev in thread] [next in thread]