Announcing the creation of a new nightly release validation test event for Fedora 24 Rawhide 20151117. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/24
You can see all results, find testing instructions and image download locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_24_Rawhide_20151117_Summa...
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_24_Rawhide_20151117_Insta... https://fedoraproject.org/wiki/Test_Results:Fedora_24_Rawhide_20151117_Base https://fedoraproject.org/wiki/Test_Results:Fedora_24_Rawhide_20151117_Serve... https://fedoraproject.org/wiki/Test_Results:Fedora_24_Rawhide_20151117_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_24_Rawhide_20151117_Deskt... https://fedoraproject.org/wiki/Test_Results:Fedora_24_Rawhide_20151117_Secur... https://fedoraproject.org/wiki/Template:Fedora_24_Rawhide_20151117_Download
Thank you for testing!
On Tue, Nov 17, 2015 at 07:38:43PM -0800, adamwill@fedoraproject.org wrote:
for Fedora 24 Rawhide 20151117. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
If problems are found which we know will eventually be blockers for F24, what's the process of making sure those are on the radar of poeple who can fix them _before_ the crunch time?
I've run all openQA tests on 20151117 and it seems to work OK (after some fixes in our tests). Only two things (from what we are testing) don't work: KDE Live doesn't boot and upgrade (from F22 Desktop) doesn't work (it works with minimal though).
2015-11-18 15:57 GMT+01:00 Matthew Miller mattdm@fedoraproject.org:
On Tue, Nov 17, 2015 at 07:38:43PM -0800, adamwill@fedoraproject.org wrote:
for Fedora 24 Rawhide 20151117. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
If problems are found which we know will eventually be blockers for F24, what's the process of making sure those are on the radar of poeple who can fix them _before_ the crunch time?
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Wed, 2015-11-18 at 09:57 -0500, Matthew Miller wrote:
On Tue, Nov 17, 2015 at 07:38:43PM -0800, adamwill@fedoraproject.org wrote:
for Fedora 24 Rawhide 20151117. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
If problems are found which we know will eventually be blockers for F24, what's the process of making sure those are on the radar of poeple who can fix them _before_ the crunch time?
Any problem found that violates the criteria will not 'eventually be' a blocker for F24, it already *is* a blocker for F24. The F24 blocker tracker bugs exist, the blocker nomination web UI is set up to point to F24; you can already nominate F24 blockers (in fact I nominated the first several months ago, shortly after F24 branched).
So, if we find any blockers, we will nominate them as usual. Blocker review meetings will start pretty soon also, as soon as we have a couple of bugs to review.
One step that perhaps we could improve on from last time is sending out blocker status mails earlier and more frequently, but in fact for F23, things went very well at Alpha: we identified and fixed all the blockers quite early, and shipped Alpha on schedule.
(for the record, blocker trackers are created two releases in advance; when we shipped F23, we created the F25 blocker tracker bugs.)
-
Adam Williamson -
Jan Sedlak -
Matthew Miller