I agree there is IMHO no sense in versioning 1.02
This is for me v1.0.2.x
Versioning scheme as I see it...
A = Product Major Version
B = Product Feature Release
C = Product Release incrementeal ID
D = Fix/Test/Debug/ for short the Build number
Example for a e.g. wordprocessor:
0.x = Initial development
188.8.131.52 = Initial Debug Release
184.108.40.206 = 57th testing build
220.127.116.11 = Initial "official" build
18.104.22.168 = 33rd fix for the official build
22.214.171.124 = Second "official" build including all bug fixes
126.96.36.1998 = Now we have a spell checker
188.8.131.52 = And a thesaurus.
184.108.40.2062 = And we introduced Linux compatibility because we built it with Kylix
Use this structure internally, it works very well. A customer needs to know A.B for features, A.B.C for fixes to features, and we use D internally for testing/debugging and emergency fixes for when taxes don't add up.
Success to everyone to streamline the versioning of your releases.