On Tue, Apr 14, 2015 at 06:14:13PM -0700, M. Edward (Ed) Borasky wrote: > That seems like a missing step in the test / QA process - one which > I've been force to script in my own testing process for releasing on > F22. Weren't the F21 Docker images posted to Docker Hub for anyone to > test at some point before final release? Admittedly I haven't looked > at the formal test pages on the wiki so I don't know if it's there or > not. Also, the test compose / release candidate cycle doesn't always > deliver a Docker image tarball - RC1 had one but RC2 doesn't. Part of the problem is that the docker image upload process is actually a manual pull request on github. I cc'd Lokesh, who has been handling this (thanks Lokesh!) and can maybe fill in more. [and, switching topics] > My Atomic use case is quite narrow and outside what I think is the > "mainstream" Atomic use case. I'm using it as a Docker host running > under Windows 8.1 and Windows 10 Client Hyper-V in place of > Boot2Docker or Docker Machine. Almost any Atomic build will do that > now but I'm looking for something that is slower-moving than a full > release every two weeks. A full release every Fedora release is ideal > but since that's been ruled out, the next best thing is a CentOS > Atomic that tracks RHEL Atomic. It's not completely ruled out; we're just not feeling ready for it yet. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
