Wednesday, December 10, 2003, 1:25:49 PM, MaXxX wrote:
>> To close, the release version numbers conform to programming version
>> numbering standard.
> And, if we were to use the Linux software version numbering scheme as
> well, we'd go: Major 2, Minor 02, Build 3 - with Build even for
> suspected stables, odd for known unstables. Irony? :P
Almost right, given version X.Y.Z then:
X is the major version number and changes when there is an extensive
change to the file format or library API. This number is not expected to
change frequently.
Y is the minor version number and is incremented by each public release
that presents new features. Even numbers are reserved for stable public
versions while odd numbers are reserved for development versions.
Z is the release number. For public versions, the release number is
incremented each time a bug is fixed and the fix is made available to
the public. For development versions, the release number is incremented
more often (perhaps almost daily).
Not all software follows the odd/even practice and definition of a what
constitutes a major version increase differs too. Besides that it is
mostly standard.
--
Kjartan <[EMAIL PROTECTED]>
:: "Real programmers don't comment their code. If it was hard
to write, it should be hard to understand."
________________________________________________________
Current beta is 2.02 CE RC2 | "Using TBBETA" information:
http://www.silverstones.com/thebat/TBUDLInfo.html
