Hi folks! Just a quick update on F23. We found a couple of blockers in 32-bit KDE stuff over the weekend. RC4 is spinning now, with fixes, and should be done in a few hours. I'll try and make sure someone's around to create the release pages and send out an announcement when it's ready.
There's only one non-KDE change, to gnome-software, so most of the RC3 test results can be transferred over - I'll take care of that later. We should prioritize tests that haven't been done with RC3 yet, and KDE tests.
Thanks folks!
On Mon, 2015-10-26 at 22:18 -0700, Adam Williamson wrote:
Hi folks! Just a quick update on F23. We found a couple of blockers in 32-bit KDE stuff over the weekend. RC4 is spinning now, with fixes, and should be done in a few hours. I'll try and make sure someone's around to create the release pages and send out an announcement when it's ready.
There's only one non-KDE change, to gnome-software, so most of the RC3 test results can be transferred over - I'll take care of that later. We should prioritize tests that haven't been done with RC3 yet, and KDE tests.
Updating again (and Evolution, srsly, what is wrong with your line wraps):
I messed up testing on one of the blocker fixes, so we had to fire another RC. RC6 is spinning right now. The good news again is the change is minimal, so most testing for RC3 and RC5 will still be valid. Again, we should prioritize:
* Things not tested in RC3 * KDE testing * GNOME Software
and adding another couple:
* abrt * ssh
since we added a couple more FE fixes. I'll spend a bit of time transferring RC3 and RC5 results to the RC6 tables tomorrow, and then we can try and fill in any gaps. Sorry for the mix-up!
On Tue, 2015-10-27 at 23:25 -0700, Adam Williamson wrote:
Updating again (and Evolution, srsly, what is wrong with your line wraps):
Here's another update!
We have an RC7 spinning right now. The good news is the change from RC6 is minimal: it simply adds the latest build of fedora-release-notes (all previous TCs/RCs had the F22 release notes, see https://bugzilla.redhat.com/show_bug.cgi?id=1276165%C2%A0). Nothing else is changed. So for RC7 we really only need to check the release notes are correct, and re-do the sanity checks (make sure all the images actually boot and so on) - all other results will be transferrable from RC3/RC6.
The idea is that at the go/no-go meeting we'll be able to choose between:
i) adjusting the criteria, rejecting the release notes issue as a blocker, and shipping RC6 ii) keeping the release notes issue as a blocker, shipping RC7 iii) keeping the release notes issue as a blocker, slip for further RC7 testing iv) give it all up and start a yak farm
So, it'd be great if folks can run the sanity checks (first few sections of the Installation page, basically) on RC7 when it arrives, but until then, keep testing RC6 - the RC6 results won't be wasted. Thanks!