Fedora 14 Alpha Blocker Bug Review Meeting #1 2010-07-16 @ 16:00 UTC (12 PM EST)
John Poelstra
poelstra at redhat.com
Thu Jul 15 02:36:08 UTC 2010
When: Friday, 2010-07-16 @ 16:00 UTC (12 PM EST)
Where: #fedora-bugzappers on irc.freenode.net
It's that time again: blocker bug review meeting time! Friday is the
FIRST blocker bug review meeting for the Fedora 14 Alpha.
Here are the current bugs listed as blocking the Alpha release. We'll be
discussing all of these to determine if they meet the criteria, should
stay on the list, and are getting the attention they need:
614488 :: NEW :: anaconda :: Anaconda Maintenance Team :: Dropped
vesamenu.c32 from rawhide boot.iso ::
https://bugzilla.redhat.com/show_bug.cgi?id=614488
614538 :: NEW :: firstboot :: Martin Gracik :: firstboot does not
start after manual install ::
https://bugzilla.redhat.com/show_bug.cgi?id=614538
613695 :: ASSIGNED :: anaconda :: Martin Gracik :: ImportError:
cannot import name GObject ::
https://bugzilla.redhat.com/show_bug.cgi?id=613695
If you are the owner of these bugs, kindly update the comments with your
feedback as to whether you believe it is a blocker and what your plans
for fixing the bug are.
Do you have an issue you believe should be fixed before the Fedora 14
Alpha ships? Please consider the following criteria when escalating an
issue: https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria
Our goal for Fedora 14, is to continue to make sure the release criteria
matches up with our 'gut feelings' for what needs to be fixed before
releasing. So, if you see an issue that you think should be a blocker
but doesn't meet the criteria, please add it as a blocker and mention at
the meeting that the criteria does't cover it. Thanks!
To promote a bug for consideration as a blocker, simply add 'F14Alpha'
to the "Blocks" field of the bug you are concerned about. A similar
technique works for marking bugs as blocking the Beta or Final release,
if appropriate, by using 'F14Beta' and 'F14Blocker' respectively.
Hope to see everyone on Friday.
John
The command used to generate the list of bugs above is:
bugzilla query --blocked=611990 \
--bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING
\
--outputformat="%{bug_id} :: %{bug_status} :: %{component} ::
%{assigned_to} :: %{summary} :: %{url}"
More information about the devel
mailing list