Open Stack

Hi Everyone,

So I was preparing to push the first tag as part of the move to a world with a
branchless tempest and was trying to figure out the naming convention we should
be using. The only complexity here is that we are targeting to do 4 releases a
year that coincide with the OpenStack releases and the stable branch EOL. So the
open question is how do we incorporate that information in the tag naming
scheme? Or should we bother trying to incorporate it in the name at all?

I was just going to go with the standard SemVer so this first tag would be 1.0
and then we would increment it per the normal conventions. I would also just put
the supported releases in the tag message. The concern here is that the tag
names themselves don't really indicate which releases are supported.

Clark had an interesting suggestion that we instead tag each new release
with the version and add a separate eol tag for when we drop support for a
release. So for example, the first release will be 2014.1 because it adds
support for the newly released Icehouse and when Havana goes EOL this summer
we add a 2013.2.eol tag. My only concern with doing this is that it kind of
ignores the other changes and improvements we make along the way. I also think
it would be a bit unclear with this scheme which is the most recent tag at any
given point in time. For example, is 2013.2.eol older or newer than 2014.1? I
think this would only get more confusing if we expand the length of the stable
maint. window.

I'd like to stick with one scheme and not decide to change it later on. I
figured I should bring this out to a wider audience to see if there were other
suggestions or opinions before I pushed out the tag, especially because the tags
are primarily for the consumers of Tempest.


-Matt Treinish