Releasing a new version

In order to allow someone to take care of it, here is a detailed description of the release process applied for all the alpha releases:

1. Go into the directory containing glob2 HEAD
2. Check that the local cvs is up to date (through "cvs up")
3. Check that all the required graphics and maps are in the server (through "./mkdata" and "./mkmaps")
4. Run "make dist-clean"
5. Increment version number in configure.in
6. Increment Debian version number by doing debchange -i in debian/
7. Set CXXFLAGS to "-O2 -g -march=i686", final release could be compiled without the -g and with -O3 but right now -g -O2 is a reasonable tradeoff between speed and debugability
8. Run "./bootstrap"
9. Run "./configure"; if any problem occurs, well, the HEAD is not ready for release!
10. Run "make"; if any problem occurs, well, the HEAD is *still* not ready for release!
11. Test the resulting binary; if any problem occurs, well, you should fix your code instead of releasing stuff!
12. Run "cvs tag RELEASE_NAME", in order to tag the CVS so that packagers can fetch this *exact* source tree for this release
13. Run "make dist" to make the .tar.gz
14. Run "fakeroot debian/rules binary" to make the debian package
15. Upload them to glob2@www.globulation2.org:/home/glob2/public_html/releases/X.Y.Z (for example, alpha20 = 0.8.20).
16. Send a mail to the ml, update web site, savannah news, and rest of the Worlds about the "Good news" ;-)