public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] RFC: bugzilla flags for arch-testing
Date: Mon, 26 Apr 2010 11:40:07 +0200	[thread overview]
Message-ID: <4BD55F77.2090900@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

To make it easier to find stabilization bugs with arch-testers'
comments, I'd like to add new flags to Gentoo bugzilla.

This is only an initial idea, and maybe a different implementation would
be better (like the status whiteboard, if it's easily searchable).

Initially, I'd like a new flag x86-at to be added, with states:

" " (default),
"+" (meaning that an AT has tested the package successfully on x86), "-"
(meaning that an AT found some problems preventing stabilization)
"?" (meaning a developer asks for more urgent AT testing)

What do you think? Feel free to suggest alternative implementations. The
goal is to easily find bugs where ATs posted comments that the package
is ready to go stable.

Also, I think it may be useful for other arch teams (like amd64). One
solution would be to add yet another flag, like amd64-at, but maybe we
can have some better ideas.

After a consensus is reached, I'm going to file a bug for infra for
necessary changes in bugzilla configuration.

Paweł


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2010-04-26  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26  9:40 "Paweł Hajdan, Jr." [this message]
2010-04-26 10:34 ` [gentoo-dev] RFC: bugzilla flags for arch-testing Matti Bickel
2010-04-26 10:45   ` "Paweł Hajdan, Jr."
2010-04-26 17:32 ` Robin H. Johnson
2010-04-26 18:36   ` [gentoo-dev] " Christian Faulhammer
2010-04-27  4:41 ` 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=4BD55F77.2090900@gentoo.org \
    --to=phajdan.jr@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