On Wed, Jun 22, 2016 at 10:28:32AM -0500, Adam Miller wrote: > > My main concern is that we would then introduce a concept of "next" > that isn't well defined within the Release Engineering vocabulary or > the Fedora Project at large as any sort of milestone deliverable. > (Where as in debian land "stable", "testing", and "unstable"/"sid" are > well defined streams of code/content). > > What we could do is release Fedora N+1 at Alpha, Beta, and Final times > and tag is as N-alpha, N-beta, and then finally just N (and latest). > > Example: > > Fedora 24 is current stable -> docker image:tag fedora:24 and > fedora:latest point to this. > > Fedora 25 Alpha is released -> push docker image:tag fedora:25-alpha to the Hub > > Fedora 25 Beta is released -> push docker image:tag fedora:25-beta to > the Hub (removing fedora:25-alpha tag) > > Fedora 25 GA is released -> push docker image:tag fedora:25 (removing > the fedora:25-beta tag and update fedora:latest to point to fedora:25) > > Fedora Rawhide continues rolling along as it does fedora:rawhide (we > tend to update this roughly once a month right now) > > Thoughts? Having easy way to get the next release container after Alpha and not just rawhide (which is next next by that time) would definitely be appreciated. Having the name reasonably stable for a couple of weeks would be a nice benefit, especially for automated testing. Therefore, fedora:25-alpha, fedora:25-beta would be really good. I just don't like the proposal of removing fedora:25-alpha the moment fedora:25-beta is released -- there might be a need to debug some regression and easy way to get Alpha even after Beta is out might be useful. I'd propose to remove all pre-release tags one month after the GA (fedora:25 in this example) has been made available. -- Jan Pazdziora Senior Principal Software Engineer, Identity Management Engineering, Red Hat _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
