From: Tom Reynolds <tomreyn@me...> - 2012-12-30 22:44:07
I think this hasn't been communicated, yet, so I'll do this now:
A new version / compatibility scheme has been introduced with version 3.7.1.
>From now on, any given version a.b.c (>= 3.7.1) is compatible (for
online gaming) with any other version a.b.n (n in 0..infinite).
Put differently: If 'a' indicated a major version, a.b more closely
describes a minor version 'b' on top of 'a' and a.b.c describes a micro
version pm top of 'a' and 'b', then any micro version a.b.c is
compatible to any other micro version a.b.d.
More simply yet: Any versions which are of the same major (1st position
in version number) and minor (2nd position in version number) version
are compatible if the game version is at least 3.7.1.
This also means that future releases which introduce incompatible
changes (this will probably still happen often, we're only changing the
versioning methodology/scheme, not the development goals) will be easily
noticed by an increment on the minor version (2nd position in version
Finally, this change should also allow us to get rid of versions which
are comprised of four positions (a.b.c.d).
To provide some examples:
* versions 3.7.2 to 3.7.42 will all be compatible to each other
* versions 3.7.1 and 3.8.0 will be incompatible
* versions 3.7.1 is not backward compatible to 3.7.0 (the new version
scheme is only valid from v3.7.1 onwards)
Motivation: We believe this change makes it more obvious (to both humans
and software) which versions are (not) compatible to each other, it
allows us to make it more obvious when we think that a new release
provides a whole lot of new features or improvements, and it is more in
line with version schemes of other open source software.
Comments are welcome, but please recognize this was a well considered
change and it's not going to be reverted. Suggestions for any kinds of
improvements are always welcome (as long as the suggesting party
clarifies how s/he will contribute to make it happen).