F-13 Alpha Blocker Meeting 2010-02-12 @ 16:00 UTC (11 AM EST)
by Adam Williamson
When: Friday, 2010-02-12 @ 16:00 UTC (11 AM EST)
Where: #fedora-bugzappers on irc.freenode.net
It's that time again: blocker bug review meeting time! Tomorrow is the
second blocker bug review meeting for Fedora 13 Alpha.
Please note the adjustments to the time written in this announcement.
The last meeting announcement was completely nonsensical, as I copied it
from a period when we were on daylight savings time - d'oh. We claimed
last week's meeting was at '1500 UTC (11 AM EDT)'. It actually took
place at 1600 UTC, 11 AM EST, and that's when this meeting will take
place too. Only now the announcement actually says that. :) We're not
really doing it at 1500 UTC because that's 7am over here and I'm damned
if I'm waking up that early twice a week.
Here are the current bugs listed as blocking the Alpha release. We'll be
discussing all of these:
555526 NEW doxygen #if !defined(X) broken in doxygen 1.6.2
563212 NEW xorg-x11-drv-intel xorg-x11-drv-intel-2.10.0-3.fc13.x86_64 kills display: only black screen, no server interactions....
557386 NEW kernel changes in do_coredump breaks ABRT
562209 NEW c-ares Booting boot.iso, installer unable to read network package metadata
563348 NEW rsyslog rsyslog-4.4.2-4.fc13 fails to start
560477 ASSIGNED anaconda RescueInterface instance has no attribute 'resetInitializeDiskQuestion'
Have an issue you'd like to propose as an F13 release blocker? Please
consider the following criteria when escalating an issue:
https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria
The aim for the Release Criteria for F13 is for our criteria to match up
with our 'gut feelings', 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 don't cover it. Thanks!
To promote a bug for consideration as a blocker, simply mark it as
blocking the bug 'F13Alpha'. You can also already mark bugs as blocking
the Beta or Final release, if appropriate, by using 'F13Beta' and
'F13Blocker' respectively.
Hope to see everyone at the meeting tomorrow!
For the record, the command used to generate the list of bugs is:
bugzilla query --blocked=538273 --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} %{summary}"
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
14 years, 2 months
F-13 Alpha Blocker Meeting 2010-02-05 @ 15:00 UTC (11 AM EDT)
by Adam Williamson
When: Friday, 2010-02-04 @ 15:00 UTC (11 AM EDT)
Where: #fedora-bugzappers on irc.freenode.net
It's that time again: blocker bug review meeting time! Yes, yes.
Already. Tomorrow is the first blocker bug review meeting for Fedora 13
Alpha.
Here are the current bugs listed as blocking the Alpha release. We'll be
discussing all of these:
559290 NEW anaconda LVMError: lvcreate failed for VolGroup/lv_root: 11:48:42,310 INFO : Running... ['lvm', 'lvcreate', '-L', '6760m', '-n', 'lv_root', 'VolGroup']
560334 NEW anaconda FSError: filesystem has not been created
557386 NEW kernel changes in do_coredump breaks ABRT
557928 ASSIGNED anaconda rats_install encountered 'Storage Activation Failed' - no anacdump.txt written
560477 ASSIGNED anaconda RescueInterface instance has no attribute 'resetInitializeDiskQuestion'
560017 MODIFIED anaconda DeviceFormatError: format has not been created
557323 MODIFIED anaconda UnboundLocalError: local variable 'name' referenced before assignment
559679 MODIFIED hal Starting HAL demon: /bin/bash: line 1: Trace/breakpoint trap
Have an issue you'd like to propose as an F13 release blocker? Please
consider the following criteria when escalating an issue:
https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria
The aim for the Release Criteria for F13 is for our criteria to match up
with our 'gut feelings', 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 don't cover it. Thanks!
To promote a bug for consideration as a blocker, simply mark it as
blocking the bug 'F13Alpha'. You can also already mark bugs as blocking
the Beta or Final release, if appropriate, by using 'F13Beta' and
'F13Blocker' respectively.
Hope to see everyone at the meeting tomorrow!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
14 years, 2 months
2010-02-04 - Fedora Test Day - NFSv4 by default
by James Laska
Greetings folks,
It's been quiet on the test day front for some time now. However, rest
assured, we are kicking off the Fedora 13 test day schedule in style. I
invite you to join #fedora-test-day this Thursday, February 4, 2010 for
the first of many Fedora 13 test days.
Qian Cai and Steve Dickson will be guiding test and triage as we
validate the Fedora 13 feature 'NFSv4 by default' [1]. Cai is putting
some finishing touches on the test cases now. However, for those
unfamiliar with testing NFS, you'll get a chance to run the upstream
test suite 'connectathon' in several different environments. In
addition to the posted test cases, you're encouraged to join and
validate running the latest NFS in your environment.
Given how early it is in the release cycle, Rawhide *and* Fedora 12 can
also be used to participate. Don't have a spare system? Not to worry.
The type of testing planned can also be done using virtual guests.
For more information on the event, check out the wiki at
https://fedoraproject.org/wiki/Test_Day:2010-02-04_NFS.
Hope to see you in #fedora-test-day this Thursday.
Thanks,
James
[1] https://fedoraproject.org/wiki/Features/NFSv4Default
14 years, 2 months
