semantic versioning

[rade]

Currently (as of #10) the weave router container versioning uses the github revision. In #33 we plan to introduce versioning of the weave script. And #34 covers compatibility checking between the two. It's hard to see how we can do the latter w/o semantic versioning. And, more generally, semantic versioning is useful to our users. See, e.g. #109.

[hesco]

Thanks rade, for moving this request forward.

As a way to get you going on the implementation of this requested feature,
let me share with you code I just committed to the hesco-weave puppet module project.

See specifically:
https://github.com/hesco/hesco-weave/blob/master/Makefile
https://github.com/hesco/hesco-weave/blob/master/scripts/set_version.sh

These two files implement the architecture I had suggested in #109,
for the puppet module I am working on. You know, that geese and gander thing.

Hope this permits you to quickly deliver so that I can enable upgrade/downgrade
of the weave script in the puppet module for managing a weave installation.

Thanks again.
-- Hugh

[hesco]

Also, at the risk of stating the obvious, I would urge that the versions
for the router container and for the script be the same version.
No reason I can think of to manage two distinct versions numbers for them.
It would simplify determination of compatibility.

[hesco]

A wrinkle I at first missed of the semantic versioning standard published at semver.org is the no-leading zero's rule. In the code above, I depend on the user to set the major and minor versions (with git tag) and let this script set the patch version (using git describe --tags). Next iteration, I will add a check for the leading zero rule and abort the make release process if one is found. The puppet forge is apparently wired to reject package uploads which include leading zeros in their version numbers.

[hesco]

#165

[errordeveloper]

I think this can be close as #263 has landed.

[rade]

Closed by #263.