Re: Reminder: impending GNOME 1.4 RC1 deadline

[Martin Baulig <martin home-of-linux org>]

Maciej Stachowiak <mjs eazel com> writes:

> Karl Eichwalder <keichwa gmx net> writes:
> 
> > Maciej Stachowiak <mjs eazel com> writes:
> > 
> > > Since our goal is not to change anything between RC1 and final unless
> > > there are major showstoppers, you should build these packages as if
> > > they are final. That is, set all version numbers to be something GNOME
> > > 1.4 final looking (so no 1.3.x's, no whatever-beta2's, etc).
> > 
> > But if it's needed to change anything for the final release you'll have
> > to increase the 1.4 version (1.4.1)!
> > 
> > Never ever release differents contents with the same version number,
> > please.
> > 
> 
> Yes, I thought this went without saying, if you do need to do an
> emergency respin, it will have to be called 1.4.1 or whatever. Deity
> willing, this will be unnecessary.

Why don't we just call all our packages 1.3.99.xx and then update the version
numbers to 1.4.0 right before the final release but without changing anything
in the tarball.

I remember that we did this in the GNOME 1.0 days.

This works fine if you use CVS tags and then make the final 1.4.0 packages
from the same CVS tag but just with the incremented version number. And when
you're done with it, you unpack both the beta and the final tarball and run
a `diff -ruN' over then to make sure you didn't modify anything except the
version number.

This is how I did with all my GNOME 1.0 tarballs.

-- 
Martin Baulig
martin gnome org (private)
baulig suse de (work)