"Major Version 0, Minor Version 99" can be written as v.0.99 or v.[0, 99] or v.[[Major, 0], [Minor, 99]] or VersionID "0-99" or Version: 0/99 among others.
"Major Version 0, Minor Version 100" can be written as v.0.100 or v.[0, 100] or v.[[Major, 0], [Minor, 100]] or VersionID "0-100" or Version: 0/100 among others.
"Major Version 0, Minor Version 100" should not be written as [1, 0], or [[Major, 1][Minor, 0]] or Version: 1/0 as that could clearly cause confusion.
Additionally, B versions do not need to be explicit (nor do Minor Versions)
Version: 1, could be followed by Version: 1/1 which could be followed by Version: 1/1/1
Version: 1/9, could be followed by Version: 2, or Version: 1/10, or Version: 1/9/1
v.0.100 could be followed by v.0.100.B (which would mean that "A" was implied originally.)
I used to name my versions using a lead zero, so that versions would start at
Major Version: 0, Minor Version: 01 and go up from there. My files could therefore be named as 0.01, 0.02, 0.03, and so on. The problem is that the files became hard to search for when I managed to reach Version 0.100, so I made one folder for the first 100 minor patches, then another for later ones.
examples:
\Archive\minorversion0-99\[insert name].v0.99
\Archive\minorversion100-999\[insert name].v0.321
If I had reached 1000, I would've just made another folder.
-
You fail to acknowledge that the dot between 0 and 99, is not intended to be used as a radix point.
Would you have the same problem if version: 0,99 was followed by version: 0,100?
