Atomic 2 week releases

[Adam Miller]

On Mon, Mar 9, 2015 at 10:34 AM, Michael P. McGrath <mmcgrath at redhat.com> wrote:
> Hey all, I wanted to start a thread about doing more frequent Atomic releases in Fedora.
> In particular I'd like to start building a new atomic release every two weeks that
> includes the latest version of Docker, Kubernetes, and OSTree for the Fedora Atomic
> images.
>
> The problem I'm trying to solve here is that there is a lot of work going on upstream in
> the Docker and Kubernetes communities and there isn't a very good way to consume that
> upstream work on a Red Hat/Fedora/CentOS system today.  By focusing on more regular
> releases, we can fix some of the issues we've seen (like demoing new features at a
> conference that people can't actually use).
>
> There are still some details to work out like whether to base this image on Fedora
> $CURRENT or rawhide and what to do when the builds fail.  Fortunately, this can possibly
> be done without much additional change to the release process.  We're already rebuilding
> the docker/kubernetes/ostree rpms almost daily, and there are nightly builds as well
> (at least in rawhide).

For those not familiar with the current release process of Atomic, can
you provide a link to documentation on how that is done as well as
what tooling is involved?

Thank you,
-AdamM

>
> If we can pull a 2 week process off, I'd like to see that followed by a 4 week process
> in CentOS which will behave similarly but with the slightly slower-moving, more stable bits.
>
> Thoughts?
>
> [1] http://www.projectatomic.io/download/
>
> --
> Mike McGrath | mmcgrath at redhat.com | (312) 660-3547
> Atomic | Red Hat Chicago | http://projectatomic.io/
> _______________________________________________
> cloud mailing list
> cloud at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/cloud
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct