Hey, folks. So I've belatedly put the F19 QA Retrospective page up here:
https://fedoraproject.org/wiki/Fedora_19_QA_Retrospective
For the newer folks or those older folks who've forgotten, the
Retrospective page aims to gather feedback on the test/validation
process as we go through it. It's a place to note things that are
working well and things that are working not so well. The idea is that
once the release is done, we can go through it and come up with some
action items to improve things ahead of the next cycle.
It's really meant to be up throughout the cycle so when we notice
something good, or a problem, we can throw a note in there immediately
so it's not lost, but I forgot to create it earlier: my apologies.
Please, if you have any feedback on how the Fedora 19 validation cycle
went, do add it to the page! In a week or two I'll go through the
feedback and try to convert it into action we can take prior to Fedora
20 Alpha.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
At the Fedora 19 Final Go/No-Go Meeting that just occurred, it was
agreed to Go with the Fedora 19 by Fedora QA, development, release
engineering and FPM.
Fedora 19 will be publicly available on Tuesday, July 02, 2013.
Thank you everyone for heroic effort on this release!
Meeting details can be seen here:
Minutes: http://bit.ly/12oSkZZ
Log: http://bit.ly/1csjMro
The Cat: http://bit.ly/11M5q3V
Jaroslav
We should've known it was too good to last!
Martin Banas fortunately caught a major bug in RC2 overnight:
https://bugzilla.redhat.com/show_bug.cgi?id=978852
so we are currently testing RC3 which includes a fix for that. RC3 has
not technically been released yet, but the main images - DVD, netinst,
and release blocking live images - for both primary arches are already
built and in place, so we can get the important testing done.
The RC2->RC3 delta is very small; just a change in anaconda's text mode
software selection spoke, and an incidental change in comps which we
were forced to include as it's hard to back out of comps changes. So
most RC1 and RC2 testing should remain valid.
I have transferred the RC2 results to the RC3 matrices, leaving
strategic gaps for tests we really ought to re-run for safety. In
particular we should at least test that _every release blocking image_ -
those mentioned above - is bootable, under size, works with checksum
verification and isn't broken in some weird way. We should verify the
blocker fix (I've done that already) and run a few other text installs
just to test there's no other major borkage in text mode.
We're aiming to get essential testing done on RC3 today and, assuming it
passes and no other blockers are unearthed, go ahead and sign off on
release later today: the Go/No-Go meeting is being held open to allow
this. So if people could help out with the essential RC3 tests that'd be
really great. The ones left 'open' on the matrix are the key ones we
should run, plus any 'previous RC1 run' or 'previous RC2 runs' that we
can replace with an RC3 test is great. It's probably not necessary to
bother with Base or Desktop testing as they should be 100% unchanged
from RC2.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
In case you're asking the question in the topic: you may notice there is
now an 'RC2.1' in the TC/RC download directory.
This is a respin of only the KDE live (and one non-blocking spin that's
based on it), including this update:
https://admin.fedoraproject.org/updates/FEDORA-2013-11724/liveusb-creator-3…
which simply fixes this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=976415
The change is very isolated. The package is not on the DVD nor on any
other live images, and the change affects only liveusb-creator. All RC2
testing (including all other KDE testing) remains valid except this
single test case:
https://fedoraproject.org/wiki/QA:Testcase_desktop_menus
for KDE, which I will re-test with the new image shortly. If no other
blockers are found in RC2, we will ship the RC2 images for everything
besides those two live spins, along with the RC2.1 builds of those two
live images, as Fedora 19 Final.
Please continue testing RC2 as normal, so we can have as much test
coverage as possible before tomorrow's go/no-go meeting. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
Fedora 19 Release Candidate 1 cloud images are now available from:
http://dl.fedoraproject.org/pub/alt/stage/19-RC1/Images/
in either qcow2 or raw.xz format. You should be able to use Glance in
OpenStack to just import the qcow2 images directly and go.
They're also in Amazon EC2 in the US East region (us-east-1):
ami-79196a10 for x86_64
ami-ef1b6886 for i386
Thanks to Dennis Gilmore in Fedora Release Engineering for the extra work to
make this happen.
The images are configured with "fedora" as the default user with
passwordless sudo. You can change this behavior by passing different
configuration data via the user-data in either OpenStack or EC2. For
example, to allow direct root login and to suppress the creation of the
'fedora' user, use
#cloud-config
users:
disable_root: 0
(The first line is identifying the userdata type, not a comment.)
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 19.
Thursday, June 27, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine if the release criteria are met for a particular release.
This meeting is called the Go/No-Go Meeting."
"Verifying that the Release criteria are met is the responsibility of
the QA Team."
For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting
In the meantime, keep an eye on the Fedora 19 Blocker list:
http://qa.fedoraproject.org/blockerbugs/milestone/19/final/buglist
There are currently three unresolved accepted blockers, for full
status see mail [1] by adamw. Please help with the release of
Fedora 19, take a look on bugs assigned to you!
Reminder: the Readiness meeting follows up the Go/No-Go meeting two
hours later.
[1] https://lists.fedoraproject.org/pipermail/devel/2013-June/184345.html
Jaroslav