> On Tue, Apr 11, 2017, at 02:09 PM, Adam Miller wrote: >> On Thu, Mar 23, 2017 at 10:14 AM, Colin Walters <walters@xxxxxxxxxx> wrote: >> > https://bugzilla.redhat.com/show_bug.cgi?id=1435310 >> > raised the issue that apparently, Atomic Host isn't "release blocking". >> > I think we have plenty of resources to match whatever criteria >> > there are for that for Fedora 27. Thoughts? >> >> Does it make sense for Atomic Host to be "release blocking" when we >> can just release every two weeks (or really whenever we want) where as >> traditional release is bound to the standard cycle? It's loosely >> coupled. > > 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. There's no reason something like that can't be treated the same as the Alternate Architectures where it's not blocking but is done as an automatic feature enhancement, so it doesn't cause a respin of the entire compose but it's pulled in if there's a new RC done. _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
