John Poelstra wrote:
Hi,
I'm trying to meet a (probably overly aggressive) personal goal of having zero NEW rawhide bugs (which are not Package Reviews) by the time of Fedora 10 GA. Along the way I thought I'd post some of the questions and issues I see while triaging these bugs so we can all learn. I encourage others to do the same. I've just knocked the list down to close to 500!
If you want to join in and help the query for NEW rawhide bugs excluding package reviews is here: http://tinyurl.com/6llac8
I just closed https://bugzilla.redhat.com/show_bug.cgi?id=446389 ;-) One more off the list ;-)
# Should this be considered a blocker? Do we have any requirements about being able to build all packages from source before GA? https://bugzilla.redhat.com/show_bug.cgi?id=462971
I think we do... but I can't recall where.
# does anyone have a labeled USB disk handy that could try this? https://bugzilla.redhat.com/show_bug.cgi?id=463106
I could, give me a day or two. Comment in bug.
# How should we be triaging "branch" and other CVS type requests ? https://bugzilla.redhat.com/show_bug.cgi?id=463105 https://bugzilla.redhat.com/show_bug.cgi?id=463397 https://bugzilla.redhat.com/show_bug.cgi?id=463175 https://bugzilla.redhat.com/show_bug.cgi?id=463139
I don't think we should, but who am I ;-)
# This CVS request has comment saying "it is done". Can bug be closed or where can I check to help verify and then close bug? https://bugzilla.redhat.com/show_bug.cgi?id=463124 https://bugzilla.redhat.com/show_bug.cgi?id=463105 https://bugzilla.redhat.com/show_bug.cgi?id=463175
Normally a Review/CVS request stays open until the package is built and submitted to updates or lands in rawhide. If the package is only landing in rawhide though there is no automagic bug closing (like bodhi can do when you submit the build to updates/ or updates-testing/).
# is this critical enough to be a blocker? https://bugzilla.redhat.com/show_bug.cgi?id=463054 https://bugzilla.redhat.com/show_bug.cgi?id=463048 https://bugzilla.redhat.com/show_bug.cgi?id=463047
Here's another one I don't think is important enough to be a blocker:
https://bugzilla.redhat.com/show_bug.cgi?id=462601
# This bug is assigned to a defunct email address... how will this bug be addressed? https://bugzilla.redhat.com/show_bug.cgi?id=462671
It says in comment #2 that it is fixed as well. Should this not be closed NEXTRELEASE (or CURRENTRELEASE?).
Kind regards,
Jeroen van Meeuwen -kanarip