Fedora 14 test release blocker bugs

Adam Williamson awilliam at redhat.com
Wed Jul 7 20:08:06 UTC 2010


On Wed, 2010-07-07 at 13:01 -0700, Jesse Keating wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 7/7/10 5:43 AM, James Laska wrote:
> > If there is a solution that addresses the problems identified during
> > F-13, and it can be implemented in *short* time.  It would be
> > compelling.  I'm a fan of solving problems with tooling, but I'm not
> > convinced that is where our big investment should be for the upcoming
> > release, or that it fully addresses the problems encountered during
> > F-13.
> 
> I can think of one quick and simple way of doing this.
> 
> When we review a bug and accept it on the blocker list, we use a keyword
> of "ACCEPTED" or some such.  That way any bug without the word is
> assumed to just be proposed and not yet accepted.  A bit more manual
> work and a bit harder to query, but it still nets the result of
> differentiating between bugs that are proposed and bugs that are
> accepted blockers.
> 
> Thoughts?

keywords we have to ask to be added to the system, I'm not keen on doing
that as a temp hack. Whiteboard space is freeform, though. We could just
pick a word to use in the whiteboard space - AcceptedBlocker, for e.g. -
and go with that.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net



More information about the devel mailing list