Closed about a 100 anaconda bugs marked as modified and commented as
fixed in cvs. The original idea behind marking them as modified was a QA
process to verify them. In reality they just lag behind in bugzilla. So
we just need to test it out using the FC-X test versions. Original
reporters can reopen it if necessary. Others can file a new one and
refer to the older bug report if they are aware of it for additional
details. Jeremy has agreed to close them immediately after fixing them
in the future
This is an easy method to track all the incoming bugs if you would like
to keep an eye on them
Would be nice to have a mailing list that triaging people can subscribe to
Hey gdk, dkl, fedora-triage. I was talking a bit about this in
#fedora-bugs, and mether suggested that I send an email about it.
Right now bugzilla.redhat.com uses resolutions (CURRENTRELEASE,
NEXTRELEASE, RAWHIDE, ERRATA) and a plain-text "fixed in" field to
denote when a bug was fixed.
I suspect that things work this way because bugzilla.redhat.com started
on a very old Bugzilla version, long ago.
In modern Bugzilla, the Target Milestone field would be a more usual
way to handle this. For closed bugs, it indicates the version that the
bug was fixed in. For open bugs, it indicates the version that the bug
is *planned* to be fixed in.
That has the added advantage of allowing developers to organize their
bug lists by when they plan (or when the project manager plans) to fix
Target Milestones also come from a drop-down box, meaning that they are
a well-defined list which is easy to search on, and people don't have to
remember exactly how to write their version numbers for "fixed in."
In general, I think the Target Milestone field could be a better
solution than what's being used now. Even if there are other internal
reasons that Red Hat needs the current resolutions, I'm sure that those
could be handled using other features of Bugzilla.
-Max (Release Manager, Bugzilla Project)
Competent, Friendly Bugzilla Services. And Everything Else, too.
We need to take this idea forward
Frequently searched queries should be made into quick links for triaging
people to go through them easily. If anyone is working on triaging bugs
it would be a good idea to post reports frequently so that we know whats
There are a few things that the Mozilla triage team uses that could be
beneficial to our BugZappers team.
Basically, developers need a way of saying:
"This bug needs some QA!"
And BugZappers need a way of saying:
"This bug has a test-case attached to it!"
On bugzilla.mozilla.org, we do this with the "keywords" feature of
Bugzilla. "Keywords" get added to the (duh) "keywords" field on the bug.
They are certain strings that you can pick from a list, to get more data
about the bug.
You can see the current bugzilla.redhat.com keywords here:
Right now, the ones that would be useful for us are "EasyFix" and
"Patch." We could also add another one, "QAWanted," and another,
"TestCase." "QAWanted" would mean, "This bug needs attention from QA."
"TestCase" would mean, "this bug has a minimal test case attached that
shows the problem very clearly."
We would also need a bit of documentation on how to create a minimal
These allow developers to search for bugs that are actually easy to
fix, or that have some useful information on them.
It's possible that currently developers don't search by keywords, but
that's because there isn't a triage team to put keywords on bugs. If
keywords were actually there and useful, then developers would be more
likely to search on them.
Once the keywords are actually used and in place, we can start
explaining to developers how to make their lives easier by searching on
keywords in Bugzilla's "Advanced Search" interface.
Friendly, Competent Linux Services, and Everything Else, too.
-----BEGIN PGP SIGNED MESSAGE-----
I would like to use RAWHIDE too. Is there a way to run it, without
deleting/killing my current system. Something like on a virtual server
and an howto for installing it?
Maybe a little bit n00bish, but I simply can't get it :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----