On 03/10/2015 01:09 PM, Michael P. McGrath wrote: > ----- Original Message ----- >> From: "Daniel J Walsh" <dwalsh@xxxxxxxxxx> >> To: "Fedora Cloud SIG" <cloud@xxxxxxxxxxxxxxxxxxxxxxx> >> Sent: Tuesday, March 10, 2015 11:31:27 AM >> Subject: Re: Atomic 2 week releases >> >> >> On 03/09/2015 12:03 PM, Michael P. McGrath wrote: >>> ----- Original Message ----- >>>> From: "Daniel J Walsh" <dwalsh@xxxxxxxxxx> >>>> To: "Fedora Cloud SIG" <cloud@xxxxxxxxxxxxxxxxxxxxxxx> >>>> Sent: Monday, March 9, 2015 10:45:42 AM >>>> Subject: Re: Atomic 2 week releases >>>> >>>> >>>> On 03/09/2015 11:34 AM, Michael P. McGrath 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). >>>>> >>>>> 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@xxxxxxxxxx | (312) 660-3547 >>>>> Atomic | Red Hat Chicago | http://projectatomic.io/ >>>>> _______________________________________________ >>>>> cloud mailing list >>>>> cloud@xxxxxxxxxxxxxxxxxxxxxxx >>>>> https://admin.fedoraproject.org/mailman/listinfo/cloud >>>>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >>>> I guess the question here would be around where we would do the releases? >>>> >>>> In a perfect world, I would like to see "Daily" releases in Rawhide, as >>>> long was we had an installable >>>> tree. Every two weeks would be in Fedora Stable. If others wanted to >>>> back port to Fedora Stable-1 >>>> that would be ok, but I don't see that as the primary focus. >>>> >>>> We would be doing a lot of this with the Docker Devel branch, along with >>>> some patches that we are experimenting >>>> with. >>>> >>>> I am sure K8s would be doing something similar. >>>> >>> What version of docker would be in Fedora $CURRENT? stable or devel? And >>> would that version go out to both Atomic Fedora *and* regular Fedora users >>> or just Atomic Fedora? >>> >>> -Mike >> Those are the questions I would like to have answered. > Stable in current, devel in rawhide. We just don't yet have the toolchains to > split different versions of our packages onto the same Fedora. We'll have to > see if there's a way to do it when Adam joins up. > > -Mike I was thinking a long the lines of putting a new docker package into updates at the same time we release it to atomic. Then after a couple of weeks releasing the docker package to updates. But yes we will be shipping docker upstream minor releases as updates along with some experimental patches (Patches that have not made it upstream yet.) >>>> _______________________________________________ >>>> cloud mailing list >>>> cloud@xxxxxxxxxxxxxxxxxxxxxxx >>>> https://admin.fedoraproject.org/mailman/listinfo/cloud >>>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >>>> >>> _______________________________________________ >>> cloud mailing list >>> cloud@xxxxxxxxxxxxxxxxxxxxxxx >>> https://admin.fedoraproject.org/mailman/listinfo/cloud >>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >> _______________________________________________ >> cloud mailing list >> cloud@xxxxxxxxxxxxxxxxxxxxxxx >> https://admin.fedoraproject.org/mailman/listinfo/cloud >> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >> > _______________________________________________ > cloud mailing list > cloud@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/cloud > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
