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. I would like be clear that I'm not saying or suggesting it either is or it isn't, but I'm not convinced either direction and I'm curious what others think about the justification of not being tightly bound to the release cycle. -AdamM > _______________________________________________ > cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
