On 10/30/2015 05:21 PM, Colin Walters wrote: > On Wed, Oct 28, 2015, at 08:06 PM, Matthew Miller wrote: >> On Wed, Oct 28, 2015 at 06:45:09PM -0400, Dusty Mabe wrote: >>> Right now the last booting atomic image is TC11. If we don't do >>> another compose then we won't have an atomic image for release. >> >> Can we release the two-week-atomic autocloud build? > > My understanding in the state of > https://bugzilla.redhat.com/show_bug.cgi?id=1276775#c4 > is that F23 Atomic Host will release with the rest of F23, > but I don't think it makes sense to do so with this bug. > > Can we drop it out of the release set of images and then > revisit doing it in two weeks? Question: Will this affect rpm-ostree upgrades? Will workarounds be too onerous for 2 weeks? I'm OK with pushing Atomic release out two weeks if we are relatively confident in a release and having this fixed by then. (That would be 17 November, right?) Best, jzb -- Joe Brockmeier | Community Team, OSAS jzb@xxxxxxxxxx | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
