[Mnet-devel] EGTP status / problems

[Whiel O'Zookocronx]

On 2004, Aug 08, , at 09:46, baka at baka.baka wrote:

> in 0.7.1 several changes got applied to EGTP, and there will be more.

By the way, our current version numbering scheme, which I just wrote 
fresh documentation for yesterday [1], doesn't allow us to bump any 
version number except the nano version number unless we make a full, 
stable, public release.  By that policy, we shouldn't bump the micro 
version number (0.7.0 to 0.7.1), even though there were huge 
incompatible changes.

Here is the new documentation about this version number scheme.  I 
don't know whether we ought to revert the version number to v0.7.0, or 
change this scheme, or what.

# End users see version strings like this:

# "1.0.0"
#  ^ ^ ^
#  | | |
#  | | '- micro version number
#  | '- minor version number
#  '- major version number

# The first number is "major version number".  The second number is the 
"minor
# version number" -- it gets bumped whenever we make a new release that 
adds or
# changes functionality.  The third version is the "micro version 
number" -- it
# gets bumped whenever we make a new release that doesn't add or change
# functionality, but just fixes bugs (including performance issues).

# Early-adopter end users see version strings like this:

# "1.0.0a1"
#  ^ ^ ^^^
#  | | |||
#  | | ||'- release number
#  | | |'- alpha or beta (or none)
#  | | '- micro version number
#  | '- minor version number
#  '- major version number

# The optional "a" or "b" stands for "alpha release" or "beta release"
# respectively.  The number after "a" or "b" gets bumped every time we
# make a new alpha or beta release. This has the same form and the same
# meaning as version numbers of releases of Python.

# Developers see "full version strings", like this:

# "1.0.0a1-55-UNSTABLE"
#  ^ ^ ^^^  ^     ^
#  | | |||  |     |
#  | | |||  |     '- tags
#  | | |||  '- nano version number
#  | | ||'- release number
#  | | |'- alpha or beta (or none)
#  | | '- micro version number
#  | '- minor version number
#  '- major version number

# The next number is the "nano version number".  It is meaningful only 
to
# developers.  It gets bumped whenever a developer changes anything 
that another
# developer might care about.

# The last part is the "tags" separated by "_".  Standard tags are
# "STABLE" and "UNSTABLE".

Regards,

Zooko

[1] http://mnetproject.org/repos/pyutil/pyutil/version.py