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@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
