On Wed, Jun 22, 2016 at 8:43 AM, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote: > > I could definitely see value in having these images be more > accessible. We could even make it be a different name than `fedora` > so that people know they are using something that is pre-release. > > `fedora24prerelease` with tags of date timestamps and `latest` follows > latest prerelease. > > I don't know how hard this is to achieve, just describing ideal > scenarios. tl;dr - I'm going to suggest we add a 'next' tag for the upcoming releases if that's feasible. Anybody know how other projects handle this? What's the most useful flow for people building on our container images? * Alpine has tags for 3.1 -> 3.4 (also "latest") and then "edge" * Debian has 8.5, 8, jessie, latest and then oldstable, sid, stretch, testing, unstable... * Ubuntu, afaik, doesn't have any pre-release images. They have 16.04, 15.10, 14.04, etc. (also with their release names, xenial, wily, trusty, etc.) My thought is we'd want all current versions still receiving updates, plus rawhide, plus the upcoming release. My suggestion would be to add a tag for "next" that is the upcoming Fedora release. Thoughts, comments, flames? Best, jzb -- Joe Brockmeier | Community Team, OSAS jzb@xxxxxxxxxx | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
