Fedora 19 Alpha status: blockers, karma requests etc

[Adam Williamson]

Hi folks! Time for the first blocker status mail of the Fedora 19 cycle. 
The tl;dr summary:

Karma needed for:

* 
https://admin.fedoraproject.org/updates/FEDORA-2013-5141/systemd-201-1.fc19,initial-setup-0.3.4-3.fc19
* 
https://admin.fedoraproject.org/updates/FEDORA-2013-5027/libreport-2.1.3-2.fc19

Input needed from blocker voters and developers on:

* https://bugzilla.redhat.com/show_bug.cgi?id=947142

QA folks, we need to complete the validation tests for RC1:

https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Install
https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Base

Longer version follows.

I'm touching every wooden object in sight right now, but things are 
actually looking quite good for the Alpha. There are only two open 
accepted blocker bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=929403
https://bugzilla.redhat.com/show_bug.cgi?id=926916

and both are in VERIFIED state, indicating that they have been confirmed 
fixed in Alpha RC1, but the updates need karma to be pushed stable to 
close the bugs. So if folks could provide karma on these updates:

https://admin.fedoraproject.org/updates/FEDORA-2013-5141/systemd-201-1.fc19,initial-setup-0.3.4-3.fc19
https://admin.fedoraproject.org/updates/FEDORA-2013-5027/libreport-2.1.3-2.fc19

it would be very helpful. Both are relatively easy to test.

For the systemd/initial-setup update, simply install Alpha RC1 and 
confirm that the initial-setup tool runs at first boot. It looks a lot 
like anaconda and lets you create a user account and set the root 
password if you did not already do so. The facts that it offers user 
account creation even if you already did it in anaconda, and that both 
it and gnome-initial-setup run on GNOME installs, are both known; they 
are bugs, but do not block the Alpha release.

For the libreport update, check that, if anaconda crashes, you can file 
a bug on the crash by following the steps. In previous Alpha composes, 
this didn't work. If you can't make anaconda crash, there are 
instructions for faking a crash in the test case: 
https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla 
.

We currently have only one proposed blocker bug:

https://bugzilla.redhat.com/show_bug.cgi?id=947142

input on that from blocker voters and relevant developers would be very 
helpful. It is quite hard to decide on the blocker status of the bug 
without some kind of information on how many UEFI systems it is likely 
to affect. Of course, the sooner a fix or workaround can be devised, the 
better.

Aside from the above, we need to complete the Alpha level validation tests:

https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Install
https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Base

We already covered quite a lot of the ground with previous builds, but 
we need to make sure to check everything and catch any other lurking 
blockers.

Thanks everyone, and let's hope we can get the Alpha out on time for 
once! Go/no-go is on Thursday, so we need to have a build fully tested 
without blockers by then.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net