On Tue, Apr 11, 2017 at 02:32:09PM -0400, Colin Walters wrote: > The concrete thing I'm trying to achieve is that bugs like > https://bugzilla.redhat.com/show_bug.cgi?id=1435310 > are able to be fixed during freeze time. It's exceedingly > strange to me that we had to structure the request as affecting > the "Cloud Base" image just to satisfy the process. It didn't have to be "structured" as affecting the Cloud Base image to get it in. It only was accepted *because* it affected the Cloud Base image. If it hadn't impacted the Base image, it wouldn't have been accepted because of how the Release Criteria are written and that Atomic doesn't currently block release. That said, SELinux issues tend to crop up this time during release, and it takes time for the policy to get updated. It would have only blocked Final - had the problems persisted. As it stands, if the Atomic WG files for Freeze Exceptions when we encounter bugs with our deliverables, I really don't expect to see much complaint from the QA team during blocker review (which is when we also go over Freeze Exception Requests). > There are other possibilities - we could carry "overrides" in just FAH. > That would be useful in a variety of circumstances of course, but > carries its own risks/rewards. > > To turn this around again - feel free to propose *alternate solutions*, > but just questioning the rationale doesn't make sense to me, because > that bug is an example of where (IMO) the process is broken. My "alternate solution" at this point is to file for FE status with a solid rationale on what needs fixed and why. Provided we're not looking to push in a new kernel or something crazy, I don't foresee us having any issues getting fixes in. And it also fits within the current process we're already following in the rest of Fedora. It might still be good to have a wider discussion to clear up confusion about where and how Atomic fits into the greater Fedora release process so we have something more concrete to go off of for F27. // Mike -- Fedora QA _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
