Fedora 21 Final Release Candidate 5 (RC5) Available Now!
by Adam Williamson
NOTE: Signing of the RC5 checksums is not yet complete. To be sure we're
testing the right bits we should remember to check that the images we
test match the signed checksum files once they're available, and of
course you can carefully check the TLS certificate of the server when
downloading the images. fedup tests may require the --nogpgcheck
parameter until the signed .treeinfo file is available. releng will
update and close the trac ticket when signing is complete.
As per the Fedora 21 schedule [1], Fedora 21 Final Release Candidate 5
(RC5) is now available for testing.
The difference between RC5 and RC4 is that the changes to python-blivet
and pyparted that were introduced in RC1 to fix bug #1166598 have been
reverted, as they were found to cause more serious problems than they
fixed. As this change affects the installer, all installation validation
tests should be run again. Existing RC4 test results for
post-installation tests will be considered valid and transferred into
the RC5 result pages; from now on, please do all testing with RC5
images.
Please see the following pages for download links (including delta ISOs)
and testing instructions. Normally dl.fedoraproject.org should provide
the fastest download, but download-ib01.fedoraproject.org is available
as a mirror (with an approximately 1 hour lag) in case of trouble. To
use it, just replace "dl" with "download-ib01" in the download URL.
Installation:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
Base:
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
Workstation and Desktop:
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
Server:
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
Cloud:
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
Summary:
https://fedoraproject.org/wiki/Test_Results:Current_Summary
Ideally, all Alpha, Beta, and Final priority test cases for each of
these test pages [2] should pass in order to meet the Final Release
Criteria [3]. Help is available on #fedora-qa on irc.freenode.net [4],
or on the test list [5].
Create Fedora 21 Final test compose (TC) and release candidate (RC)
https://fedorahosted.org/rel-eng/ticket/6031
Current Blocker and Freeze Exception bugs:
http://qa.fedoraproject.org/blockerbugs/current
[1] http://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
[3] https://fedoraproject.org/wiki/Fedora_21_Final_Release_Criteria
[4] irc://irc.freenode.net/fedora-qa
[5] https://admin.fedoraproject.org/mailman/listinfo/test
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 3 months
Fedora 21 Final Release Candidate 4 (RC4) Available Now!
by Adam Williamson
NOTE: Signing of the RC4 tree is not yet complete, there are technical
issues in releng preventing it working. To strictly be sure we're
testing the right bits we should remember to check that the images we
test match the signed checksum files once they're available, and of
course you can carefully check the TLS certificate of the server when
downloading the images. fedup tests may require the --nogpgcheck
parameter until the signed .treeinfo file is available. releng will
update and close the trac ticket when signing is complete.
As per the Fedora 21 schedule [1], Fedora 21 Final Release Candidate 4
(RC4) is now available for testing. Note that RC3 never made it out of
the compose process - releng made a small mistake so they started over,
and it was easier to call the retry 'RC4' than clean up the failed
attempt and call the retry 'RC3'.
The only difference between RC4 and RC2 should be that the live images
have correct fontconfig caches. Otherwise RC4 and RC2 should be
effectively identical. There is no difference in their package sets, the
fontconfig fix was done in the kickstarts. Existing RC2 test results
will be considered valid for RC4 and transferred to the RC4 result
pages, but from now on, please switch to testing the RC4 images.
At present we're hopeful RC4 will be good enough for Final release, so
please help us get through all the testing!
Please see the following pages for download links (including delta ISOs)
and testing instructions. Normally dl.fedoraproject.org should provide
the fastest download, but download-ib01.fedoraproject.org is available
as a mirror (with an approximately 1 hour lag) in case of trouble. To
use it, just replace "dl" with "download-ib01" in the download URL.
Installation:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
Base:
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
Workstation and Desktop:
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
Server:
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
Cloud:
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
Summary:
https://fedoraproject.org/wiki/Test_Results:Current_Summary
Ideally, all Alpha, Beta, and Final priority test cases for each of
these test pages [2] should pass in order to meet the Final Release
Criteria [3]. Help is available on #fedora-qa on irc.freenode.net [4],
or on the test list [5].
Create Fedora 21 Final test compose (TC) and release candidate (RC)
https://fedorahosted.org/rel-eng/ticket/6031
Current Blocker and Freeze Exception bugs:
http://qa.fedoraproject.org/blockerbugs/current
[1] http://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
[3] https://fedoraproject.org/wiki/Fedora_21_Final_Release_Criteria
[4] irc://irc.freenode.net/fedora-qa
[5] https://admin.fedoraproject.org/mailman/listinfo/test
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 3 months
2014-12-03 @ 1600 UTC ** Conditional Blocker Review Meeting
by Mike Ruckman
Greetings testers! Typically we'd have a blocker review meeting
tomorrow, but with Go/No-Go this Thursday and a pretty solid RC out and
being tested, we might not need one. Currently there are no proposed
blockers (and let's hope we've handled all of them), so we won't be
having a meeting.
OTOH, if we do find some tonight or before the meeting tomorrow we'll go
ahead and have the meeting to discuss whatever has been found.
Just wanted to give everyone a heads up. Thanks!
--
// Mike
--
Fedora QA
freenode: roshi
http://roshi.fedorapeople.org
9 years, 3 months
F21 testing heads up: RC3 is coming, but RC2 tests are valid, please continue testing RC2
by Adam Williamson
Just an F21 validation test status heads up.
We found a cosmetic but highly visible font issue in RC2:
https://bugzilla.redhat.com/show_bug.cgi?id=1169979 . The most obvious
effect is that at least the Workstation and KDE x86-64 lives use a
pretty ugly font 'Nimbus Mono L' as their default monospace font - the
one used in terminals and text editors, for e.g. - instead of the
intended default, DejaVu Sans Mono.
Fortunately we can workaround this problem for the live images pretty
easily and in a way which is very safe: just run fc-cache -f at the end
of the live compose process. We are now spinning RC3 with that change.
As the difference between RC2 and RC3 is so small, we're gonna say that
all RC2 testing is valid against RC3. Once the RC3 compose is done I'll
transfer the RC2 test results into the RC3 test matrix.
So, please just go ahead and carry on testing RC2 completely as normal.
Once RC3 comes out we can switch to testing those images.
The RC3 non-live images should be functionally identical to RC2.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 3 months
Fedora 21 Final Go/No-Go Meeting, Thursday, December 04 @ 17:00 UTC
by Jaroslav Reznik
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 21.
Thursday, December 04, 2014 17:00 UTC (12 AM EST, 9 AM PST, 18:00 CET)
"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."
Release Candidate (RC) availability and good QA coverage are prerequisites
for the Go/No-Go decision but meeting itself is held in any case.
For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting
In the meantime, keep an eye on the Fedora 21 Final Blocker list:
https://qa.fedoraproject.org/blockerbugs/milestone/21/final/buglist
Note: as I'll be already travelling to FAD Rheinland 2014, I could be
a bit late...
Jaroslav
9 years, 3 months
Proposal to CANCEL: 2014-12-01 Fedora QA Meeting
by Adam Williamson
I don't think there's much to discuss at present besides Fedora 21
testing, so I think we may as well just go right ahead and run a blocker
review meeting instead of the QA meeting. I'll send out an announce for
that right after this mail - usual time, but in #fedora-blocker-review,
and we'll review blockers. =)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 4 months