semantic versioning

[hyperthunk]

As per http://semver.org - I think this should be a given, although it probably isn't vitally important yet but once we get to a conceptual 0.1.0 it'll probably start to matter. Right now we're 0.0.1 IMO.

[qrilka]

What about http://www.haskell.org/haskellwiki/Package_versioning_policy ? It contradicts somewhat with semver but I presume it is a default policy for Haskell.

[hyperthunk]

@qrilka you're quite right, and it is almost certainly best to follow the recommendations you've linked to there. I think we can keep to that policy but stay pretty close to semver however, by adding stricter constraints about how the single element of the minor release is handled.

For the major release version number, we can (and should IMO) treat the two parts as distinct with regards API changes where

• for x.y.z when we're creating a new major release, we increment y if we've made API changes as a result of a hotfix/bugfix or extended an existing feature
• for x.y.z when we're creating a new major release, we increment x if we've made API changes as a result of new features
• for x.y.z when changing z, we use some suffix scheme or other to differentiate between patch (bugfix) and build version increments - that one's a bit hazy for me ATM though