Pidgin 2.1.2 vs 2.2.0 (was: Re: Revision 0e61386b7b4aa6f619e9471efed89eeec8b06574)

[John Bailey]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeff Connelly wrote:
> There is a milestone for 2.1.2 in Trac, but libpurple/version.h (from
> configure.ac) defines the version as 2.2.0. This is the log message:
> 
> | o   -----------------------------------------------------------------
> | |   Revision: 0e61386b7b4aa6f619e9471efed89eeec8b06574
> | |   Ancestor: 0c427acc272ff9aeb12c0cb21de759d197dc1169
> | |   Author: sadrul at pidgin.im
> | |   Date: 2007-08-23T06:20:05
> | |   Branch: im.pidgin.pidgin
> | |
> | |   Modified files:
> | |           configure.ac finch/libgnt/configure.ac
> | |
> | |   ChangeLog:
> | |
> | |   New API has been added. Bump the minor.
> | o   (Revision: 0c427acc272ff9aeb12c0cb21de759d197dc1169)
> |/|
> | o     -----------------------------------------------------------------
> 
> Does this mean there won't be a 2.1.2, and all tickets targeted to
> this milestone should be updated to 2.2.0? And that I can commit
> http://msimprpl.darkthoughts.net/attention2.diff? :)
> 
> -Jeff

API was introduced to fix a bug, and so we need to go straight to 2.2.0 instead
of releasing 2.1.2.  Now is the appropriate time to add additional new API if
you want to avoid inflating the minor number (which is NOT an issue we should
care about), but we still can't change existing API without causing a 3.0.0.

John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG0H2cBWJH/emdNtsRAgK4AKC4rNLIujvZuhX11qO9L+yuCk5j+QCg2XI6
W3eyDwBeC94PuWUNU0TzqVU=
=5W39
-----END PGP SIGNATURE-----