version numbering inconsistency

[Ian Young]

> On 7 Oct 2014, at 19:50, Brent Putman <putmanb at georgetown.edu> wrote:
> 
> 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.

Not wanting to necro this too much, but I just wanted to make a placeholder here that we have previously deferred a discussion about moving from subversion to git. When we get back to that post-3.0, I'm pretty sure that will end up also involving a discussion about branching strategies as that's one of git's USPs.

So, it's possible that post-3.0, we can end up with a consistent source control, versioning and branching strategy that both makes sense for us and is compatible with the other tools we're using. 

    -- Ian




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5250 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/dev/attachments/20141030/b353713a/attachment.bin