Hey folks! 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. Whether we do or not, we need to fix https://bugzilla.redhat.com/show_bug.cgi?id=1490072 , because it was accepted as a Beta blocker. I *did* send a build with the patches from the upstream bug to Koji: https://koji.fedoraproject.org/koji/buildinfo?buildID=969735 but I didn't submit an update for it yet because I thought it'd be better to co-ordinate with you folks. That build required a buildroot override for pipewire, so if we wanted to send that build out as the fix, we'd have to include pipewire in the update also. Roughly speaking I see three options: 1. Do all of 3.26.0, plus the patches for 1490072, as a mega-update, submit an FE to get it into Beta 2. Just send mutter 3.26.0 + pipewire out as an update to fix 1490072 3. Do a build of mutter 3.25.91 + 1490072 patches to fix that bug

What do you folks think? Thanks! I am on PTO for three weeks from Sunday, so I'm CCing pschindl who'll be covering compose-related duties. Petr, can you subscribe to desktop@ (if you're not subscribed already) and follow this thread?

-- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ desktop mailing list -- desktop(a)lists.fedoraproject.org To unsubscribe send an email to desktop-leave(a)lists.fedoraproject.org

From: "Kalev Lember" <kalevlember(a)gmail.com&gt; To: desktop(a)lists.fedoraproject.org Sent: Friday, September 15, 2017 2:26:34 PM Subject: Re: What to do about GNOME for Beta? 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, which in turn means nobody has started filling in testing matrices yet --- 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. 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. -- Kalev _______________________________________________ desktop mailing list -- desktop(a)lists.fedoraproject.org To unsubscribe send an email to desktop-leave(a)lists.fedoraproject.org

From: "Kalev Lember" <kalevlember(a)gmail.com&gt; To: desktop(a)lists.fedoraproject.org Sent: Friday, September 15, 2017 3:42:35 PM Subject: Re: What to do about GNOME for Beta? On 09/15/2017 12:04 PM, Sumantro Mukherjee wrote: > Hey Kalev and Adamw, > > Could we run a test day around it for this cycle? > > Kalev, if you are willing we can fix a date and run a test day around Gnome > 3.26.0 Sure, maybe the week when Beta is supposed to be released (25-29 September)? If we do it any later than that I don't think we have enough time to get the fixes we get from the test day into F27 GA any more. 2017-09-26 F27 Beta Release 2017-10-04 GNOME 3.26.1 2017-10-10 F27 Final Freeze -- Kalev

From: "Kalev Lember" <kalevlember(a)gmail.com&gt; To: desktop(a)lists.fedoraproject.org Sent: Friday, September 15, 2017 4:04:52 PM Subject: Re: What to do about GNOME for Beta? On 09/15/2017 12:26 PM, Sumantro Mukherjee wrote: > > > ----- Original Message ----- >> From: "Kalev Lember" <kalevlember(a)gmail.com&gt; >> To: desktop(a)lists.fedoraproject.org >> Sent: Friday, September 15, 2017 3:42:35 PM >> Subject: Re: What to do about GNOME for Beta? >> >> On 09/15/2017 12:04 PM, Sumantro Mukherjee wrote: >>> Hey Kalev and Adamw, >>> >>> Could we run a test day around it for this cycle? >>> >>> Kalev, if you are willing we can fix a date and run a test day around >>> Gnome >>> 3.26.0 >> >> Sure, maybe the week when Beta is supposed to be released (25-29 >> September)? If we do it any later than that I don't think we have enough >> time to get the fixes we get from the test day into F27 GA any more. >> >> 2017-09-26 F27 Beta Release >> 2017-10-04 GNOME 3.26.1 >> 2017-10-10 F27 Final Freeze >> >> -- >> Kalev > > Hey Kalev, > Lets do it on 28th , if you folks are good with it. I will start setting up > the pages. Works for me. Anyone else here who could join the test day and help answer questions folks might have? -- Kalev

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,

which in turn means nobody has started filling in testing matrices yet

--- 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.

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.