On 16/09/16, Jan Kurik wrote: > On Fri, Sep 16, 2016 at 2:27 PM, Colin Walters <walters@xxxxxxxxxx> wrote: > > > > > > On Fri, Sep 16, 2016, at 04:14 AM, Jan Kurik wrote: > >> Hi, > >> > >> may I request any feedback on this topic, and/or adding this topic to > >> the next Cloud WG meeting agenda ? > > > > It'd be nice to make Atomic Host a blocking deliverable - I think > > we have sufficient experience now and manpower to do that. > > How this should work ? I am asking because Atomic is delivered > bi-weekly and Fedora releases are delivered two times a year. Perhaps > delivering the last released Atomic build before Fedora release GA > date might work. Any other/better ideas how this should be > synchronized ? This is my understanding too. We sync up Atomic host with the latest released Fedora GA, and then follow on our normal 2-week release cycle. This does not make the 2 week atomic into the official 6month old release cycle story. Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
