: Yep. Bog standard for Open Source. Major doesn't change (although it should
: hit 1.0 some day...
Question for you about this, and general OSS dev practices - just out of curiosity.
Given this versioning scheme, which you say is quite common in OSS, are all versions 0.x.x through 1.x.x considered the same "major" version (the way 2.0 and 3.0 aren't)? So 0.1.0 and 1.9.9 are the same general architecture, etc... you only go 2.0 or 3.0 on major architectural changes, but 1.0 is just "our first architectural paradigm is now stable"? Or do major architectural changes only happen ABOVE a point-oh release, i.e. up to 1.0.0 are all the same major version, and then 1.1.0 is the first of the newer architecture? (doubful). Either way, seems like starting at 1.0.0 would make most sense, despite the connotations of 1.0 as "ready for public consumption" - if you want, just label all pre-1.0 versions as "alpha", "beta", etc. That way you can have 2.0 alphas and betas as well, concurrent with 1.x.x updates.
On that note, what number do projects usually start at? 0.1.0? 0.1.1? 0.0.1? 0.0.0?