On Fri, 2017-09-15 at 10:56 +0200, Kalev Lember wrote: > On 09/15/2017 03:55 AM, Adam Williamson wrote: > > So, Beta slipped today; the next go/no-go will be Sept 21. > > > > Given this, we probably have a window to get 3.26.0 into the Beta with > > an FE, if that seems like a good idea and you can have it ready to go > > by, say, Monday. > > Hey Adam, > > As I understand it, we haven't had a Beta compose yet, Not a candidate compose, no, but... > which in turn > means nobody has started filling in testing matrices yet ...this isn't accurate, we test nightlies constantly, throughout the cycle: https://fedoraproject.org/wiki/Category:Fedora_27_Nightly_Test_Results so in fact we *have* already run most of the desktop validation tests on the most recent nightly 'nominated' for testing. > --- so if we > include final 3.26.0 in Beta, it would be very little additional work > for QA, right? Probably makes sense to include the whole 3.26.0 then so > that we could test the GNOME that's more close to what we'll ship in F27 > final. On the other hand, the criteria for Beta aren't super onerous and openQA covers some of them, so even still, it's not a huge amount of work, no. And we have a pretty good track record with upgrades from the GNOME RCs to final not breaking things, so I'm not too worried. > We should have almost all builds lined up by now. How about this plan: I > submit a megaupdate to Bodhi today where all the 3.26.0 builds are in a > single update, so that it has time to be in updates-testing for a few > days before Monday, and then on Monday at the blocker review meeting we > make a call whether to take the whole thing? And if the vote is no, we > can split the update up on Monday and take individual bits. That sounds reasonable. I see the mega-update is in Bodhi now, thanks. I'll make sure it gets some testing. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
