Comment 10 for bug 629727

Yes, I think we're getting cleverer by far, but in danger of getting progressively weirder (Baldrick, "I have a cunning plan").

So going back, if we've already restricted ourselves to 0-9 per component and we accept that, we're pretty much at:

   Option E: 0.67, 0.68, 0.69, 0.70, ... 0.99, 1.00, 1.01. (Mark, comment #8)

or the same with three digits:

   Option F: 0.671, 0.672, 0.700, 0.710, ...

And only the major is special (and at Canonical's threshold for quality/metrics stability going forward). Two digits is what we've got at the moment; and we can adjust the in-vision glyphs in the PUA to match, and align the documentation. Version string is a straight forward writing out of the number X.YY with a perpended zero, which also meets the Debian versioning requirements. Both of these go verbatium in the string (with relevant zeros) and both /sort/ in the binary fraction correctly, even if they might not display with suffixed zeros.

The "clarification" is then that we make the documentation match the product and codify the methodology and reasoning in a readme: much like the versioning of the Ubuntu (operating system, eg. 10.04) the zeros are important when written but we can still reduce the number of them if we go with (E).