hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arun C Murthy <...@hortonworks.com>
Subject Re: Release numbering for branch-2 releases
Date Mon, 04 Feb 2013 18:43:48 GMT

On Feb 1, 2013, at 2:34 AM, Tom White wrote:

> Possibly the reason for Stack's consternation is that this is a
> Hadoop-specific versioning scheme, rather than a standard one like
> Semantic Versioning (http://semver.org/) which is more widely
> understood.
> With that scheme we would have something like
>  2.0.0-alpha, 2.0.0-alpha.1, 2.0.0-alpha.2, 2.0.0-alpha.3, 2.0.0-beta, 2.0.0
> so that the alpha and beta tags all precede the 2.0.0 GA release,
> which is the one that we make compatibility promises for.
> Whereas Arun is proposing
>  2.0.0-alpha, 2.0.1-alpha, 2.0.2-alpha, 2.1.0-alpha, 2.2.0-beta, 2.3.0

Would it better to have 2.0.3-alpha, 2.0.4-beta and then make 2.1 as a stable release?

I'm ok either way, but I want to just make a decision and move on to making the release asap,
appreciate a quick resolution.

View raw message