Well, the version numbering system has no bearing on the frequency of updates
Still, I don't see the difference between 1.0/1.01/1.02 and 1.0/2.0/3.0 -- it's still "3 versions". I say version numbers are bullshit, codenames doubly so.. just make it the release date or build number and be done with it. Automate it, and let no human ever think about it again. It's just an identifier for a specific changelog entry after all, and has no meaning by itself.
That's why I said “release cycle” – moving from numbers to “when it's ready” was definitely the key part. The trick was breaking the tyranny of significant numbers where people would hold off until they had enough features to be worthy of a major release.
Still, I don't see the difference between 1.0/1.01/1.02 and 1.0/2.0/3.0 -- it's still "3 versions". I say version numbers are bullshit, codenames doubly so.. just make it the release date or build number and be done with it. Automate it, and let no human ever think about it again. It's just an identifier for a specific changelog entry after all, and has no meaning by itself.