@dansup I guess your not using semantic versioning? Just arbitrary?
@freemo Yes, we plan to start using semver after v1.0
@dansup Any particular reason? Version 0.x.x gets special treatment under semantic versioning such that changes to the API that break backwards compatib ility do not need a MAJOR bump when on 0 (defined int he SEMVER standard). So only minor and patch versions are respected in 0.x.x
Considering this exception is there any reason not to use semantic versioning now? Seems like it will just make your life harder and your users.
@freemo yes, I am lazy and do not like writing change logs
@dansup lol fair. I mean to each their own. But just saying you could skip the changelogs and still semantically version... just means features bump minor bugs-only bump patch (Major.Minor.Patch).
Just a good habit to get into IMO, plus really useful for us users :)
@dansup That is what I meant earlier when i said Semantic versioning treates v0.x.x as special.
If you had lets say 38 MAJOR level updates in the past year and 3 MINOR level updates, since you are pre-production that would make the version v0.41.0
v1 on semantic versioning is ALWAYS the first stable release, that is defined in the spec. So by going semantic versioning now it would not cause the MAJOR version to bump as you described.
Here are points 4 and 5 from the standard that reiterate what I just said:
4. Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
5. Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.