Unless I am mistaken, the Woof-CE project will continue for several years (at least, I hope).
Thus, I propose that future versions have a three-digit number (woof-CE 0.0.4 for the next).
see /woof-CE/releases Regards,
I can't talk for others, but how I learnt it back in the 1970's with
PDP's and IBM 'stuff', and I think most others seem to have followed
since is :-.
Major is set by the group for structural changes such as when BarryK
went from T2 v6 to V7 to V8 he went from 3. to 4. to 5., T2 updating to
the V9 trunk is his 6. 'stuff', which I am following for Puppy T290.
Minor are normally used for release updates, usually for large steps in
packages or build system updates and is up to the builder. These can be
a 2-digit number with the second for something equivalent for changes
that are bigger than point fixes but not at the stage that needs a full
release, however this tends to confuse the general users so is rarely
used except for mainframes.
Point are normally used for minimal and internal bugfixes. Personally
i've always run these as 2 digits with the second digit a 0 if a public
fix (.01-09=internal, .10 could be a public update patch if needed,
.11-19=internal...). However, my preferance has always been to not
release points and use a simple patch for the particular application
with problems instead.
Now regarding woof release numbers, so far we up one minor number with every final puppy release.
Actually given that this is BK's "woof2" should be 2.x but as "woof-CE" 0.x is also reasonable.
When/if woof-next mature enough to release level then a new number in version-major is sure needed.