On Wed, Jun 22, 2016 at 8:17 AM, Joe Brockmeier <jzb(a)redhat.com> wrote:
On Wed, Jun 22, 2016 at 8:43 AM, Dusty Mabe
> 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
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,
* 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,
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?
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
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).
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)
Also, as an aside. Whatever we decide should be brought up with Fedora
RelEng as a meeting ticket to make sure the proposal is workable from
a release perspective (though I suspect it will be and will volunteer
to take that on). I'll also volunteer write up a SOP doc for Fedora
RelEng Documentation so that this information persists and is well
defined if there's future questions about it.
> Joe Brockmeier | Community Team, OSAS
> jzb(a)redhat.com | http://community.redhat.com/
> Twitter: @jzb | http://dissociatedpress.net/
> cloud mailing list