Version numbers should move to semantic versioning

[trevor-vaughan]

Using semantic versioning allows users to easily know if a change is breaking, a new feature, or just a bug fix.

[spbnick]

Thanks, @trevor-vaughan. It's already using semantic versioning, I would say, I just declared each new release as breaking everything, as we're not ready yet to really commit to compatibility :)

[spbnick]

However, it's our full intention to communicate that, and commit to it. We're just not adding numbers to the version string without need :)

[trevor-vaughan]

@spbnick Ah, I see. Could this be reflected in the tlog.spec file then? I'd like to actually start using it and it seems that there are several non-breaking changes in the pipeline that could be a 4.0.1 release.

[spbnick]

So, once we get a request for a smaller update to a release, ahead of a full release, we'll make a release with more numbers in version string. E.g. if we need some small feature released before v5, we can release v4.1. We'll have to have an explicit need/request for that, though. What exactly would you like to see in tlog.spec?

[trevor-vaughan]

Basically, I just want to see 5.0.0 or whatever so that all of my users don't look at me like I'm crazy for using one-numbered software. It's OK if it jumps to 6 at the next release but it adds artificial (but expected) confidence.

[spbnick]

So, do you mean you want all three numbers all the time in the version string?

[trevor-vaughan]

Yes, that would be it.

[spbnick]

OK, let's keep this open and do it the next release.