Re: the bug team and gnome2.2 [resent by Luis because everyone should see it]

[Andrew Sobala <andrew sobala net>]

OK, I'll throw ideas at you. Throw all of this in the new, pretty, GNOME
trashcan if you want :)

On Tue, 2002-08-27 at 22:10, Luis Villa wrote:
> *just as each package has a maintainer, each package should have a QA
> person, or a QA team, much like nautilus (at least theoretically) has
> ATM. Yaneti is the Galeon Guy, Kjartan is the GNOME1.4 core guy... we
> need more guys (and gals!) who can identify with and claim their own QA
> apps and build a relationship with the code maintainers.

And the QA guys should have written down what they have to do:

* Reproduce bugs for maintainers
* Duplicate removal
* Followup/close bugs marked NEEDINFO

Plus others?

What about libraries? Problems there are sometimes pretty hard to
reproduce, even for part-time hackers.

> *triaged keyword needs to stop meaning 'luis looked at and triaged it'
> and start meaning 'members of the QA team looked at it and triaged it.'
> How do we do that sanely, so that we aren't duplicating each other's
> work all the time? Also, we have to do this while maintaining
> consistency- how is that going to work?

Is a "qa-triaged" keyword, and strict instructions about who is allowed
to use it, good enough?

* At the moment, Luis decides which bugs are "showstoppers" for a
release and when other bugs should be targeted for. Without Luis, no-one
will be doing this...

Maybe the QA people, and/or (possibly in conjunction with) the
maintainers, need to be able to suggest (not dictate) which bugs need to
be fixed *now*. Maybe not :)

* A "Bugtable", like the Doctable, would be useful. Useful things to
include are:

-- QA contacts and if they are on holiday :)
-- No. of bugs without "qa-triaged" (or equivalent) set.
-- No. of "important" bugs (implementation depends on point above about
targeting bug-fix-times).

-- 
Andrew

"Someone needs to make a 'woops' command that reverts the hard disk to
the state it was in 20 seconds ago."
		-- me