On Wed, 2016-04-27 at 20:35 +0200, Kalev Lember wrote: > On 04/27/2016 08:11 PM, Adam Williamson wrote: > > On Wed, 2016-04-27 at 09:13 -0700, Adam Williamson wrote: > > > Hey folks! Just to keep everyone in the loop, here's what's going on > > > with F24 Beta: > > > > > > we have two outstanding accepted blockers that need fixing before we > > > can spin a 'release candidate': > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1321330 > > > https://bugzilla.redhat.com/show_bug.cgi?id=1259865 > > > > > > a kernel is building that is expected to fix the first, and hughsie is > > > testing a fix for the second as we speak. Once we have both fixes in > > > bodhi I'll request a release candidate compose and we'll hopefully have > > > time to blow through testing ahead of go/no-go. > > > > So unfortunately there was a bit of a communication breakdown between > > hughsie and myself, I think - he built the fix for the second bug in > > COPR and requested testing, but I was waiting for a Koji/Bodhi build > > for some reason. For anyone who wants to test it, the COPR is here: > > > > https://copr.fedorainfracloud.org/coprs/rhughes/f23-gnome320/build/181352/ > > > > (only built for F23 for some reason) - please do try it out and give > > feedback. But we can't do an F24 RC with this issue outstanding, > > really. We could try an extremely dodgy 'it's not really a blocker' > > fudge or some kind of heroic attempt for a drive-by packager to apply > > the changes to the official packages, but I'm not sure either of those > > is a great idea unless there's some kind of insanely pressing reason to > > get the Beta out on schedule. I'd rather take the time to consider it > > properly. > > Sorry, I had the patches ready last week, but there was a bit of > communication breakdown between me and hughsie and they never got > anywhere. If someone could double check that the libhif build in COPR > works, I am happy to do an official F24 build + a Bodhi update tonight. That's still a little slow unfortunately; compose takes 6-8 hours and we still have to *test* the thing, and the go/no-go meeting is in exactly 21.5 hours from now. At this point, so far as I'm concerned, if #1259865 stays as a blocker, we're slipping. The only non-slip option is to ship a compose without a fix for it, I think. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
