Re: Suggested even/odd convention for the micro version numbers (like cairo)

[Shaun McCance <shaunm gnome org>]

On Tue, 2007-12-11 at 10:37 +0200, Tor Lillqvist wrote:
> I humbly suggest that the versioning recommendation for the GTK+ stack
> and GNOME in general is amended for the third "micro" part of the
> version numbers to match the convention used in cairo.
> 
> See http://cairographics.org/manual/cairo-Version-Information.html .
> 
> In a nutshell, the idea is that released tarballs have an even micro
> version. The micro version is bumped both immediately before and after
> building the release tarball. The even micro number is never committed
> to SVN. In SVN the micro number is always odd.

So making the 2.12.2 release would look like this?

1) Change the version from 2.12.1 to 2.12.2 in configure.ac
2) Edit the NEWS file
3) make distcheck
4) Change the version from 2.12.2 to 2.12.3 in configure.ac
5) svn commit

Whereas it currently looks like this:

a) Change the version from 2.12.1 to 2.12.2 in configure.ac,
   unless you did a pre-release bump already
b) Edit the NEWS file
c) make distcheck
d) svn commit
e) svn cp $(url)/trunk $(url)/tags/MY_PROGRAM_2_12_2

The problem I see with the proposed scheme is that we can't
fit step (e) into it, since 2.12.2 is never in SVN.  With our
current scheme, you can do this:

  svn checkout $(url)/tags/MY_PROGRAM_2_12_2
  make distcheck

and get, in theory, exactly the tarball that's sitting on
ftp.gnome.org.  If 2.12.2 is never in SVN, that's not going
to be possible.

--
Shaun