On 2014-03-04 10:38, Aurélien Vallée wrote:
I don't really get the point of why nanomsg keeps track of a package version. That sounds good theoretically, but in practice it seems to melike a useless layer of mentally mapping package version -> soversion whendealing with library files. Why don't we just keep the autotools version for the project?
Autotools version is the semantic version. Right now it was changed from 1.0.1 to 2.1.2, which would confuse the hell out of the users should we use it as a package version.
And on a side note, if we stick to having a package version, that would benice to bump to 1.x.Labels like "0.3-beta" tend to trick users into thinking this is some kind of unstable toy library, which is not really the case. The library works well for its defined set of features, there is no major flow, so no need toplay small in that numbering.
Maybe I have been over-cautious with the version numbering. If people generally feel OK with moving to 1.0, it can be done on the next release.
Martin
