version numbering inconsistency

[Brent Putman]

On 10/7/14 11:46 AM, Cantor, Scott wrote:
>
> If we're able to agree that that is in fact what our current strategy
> is/was, then we can at least have the discussion later about how to fix
> it. I just re-read the page and it's pretty unambiguous to me that he was
> intending that 2.0-SNAPSHOT would be both the version prior to 2.0.0 and
> then later the version after. Since both can't be right...

Yes, that's my understanding as well, at least in terms of what Chad was
thinking.  E.g. 2.0-SNAPSHOT was intended to be used prior to all
releases that would be 2.0.x.  So I guess the SNAPSHOT was intended to
reflect each minor branch. 

Now, whether that actually makes sense vis-a-vis tools and standard
Maven conventions, I don't know.  I've not read yet all the references
Ian posted.  It may be that we just need to simplify this whole thing
and use a full major.minor.path always in the version, so you'd have
2.0.0-SNAPSHOT prior to 2.0.0, then 2.0.1-SNAPSHOT prior to 2.0.1, and
so forth.  However, not sure how that then meshes with Chad's proposed
late branching strategy, for each minor branch.  Maybe it works, maybe
not, needs more though.