Release guide : 

1) Change version numbers in :
	autoconf/configure.in
	libAfterBase/configure.in
	libAfterImage/configure.in
Make sure version numbers for libraries are changed as well if library has changed.
2) Run: make config
3) Commit changes with message like so "AfterStep release v 2.0.5".
4) rm ChangeLog && make ChangeLog
5) Commit changes to ChangeLogs.
6) Tag everything: cvs tag -r HEAD release_2_00_05
7) Create a release directory somewhere outside afterstep-stable tree and cd into it.
8) cvs -d:pserver:anonymous@cvs.aftercode.net:/home/cvsroot export -r release_2_0_5 -d AfterStep-2.0.5 afterstep-stable
#obsolete by #8 --- 9) mv -R afterstep-stable AfterStep-2.00.05
10) tar zcpvf AfterStep-2.00.05.tar.gz AfterStep-2.00.05
11) tar cpvf AfterStep-2.00.05.tar AfterStep-2.00.05
12) bzip2 AfterStep-2.00.05.tar
13) Prepare noimages tarballs like so : 
14) cp -R AfterStep-2.00.05 AfterStep-2.00.05-noimages
15) cd AfterStep-2.00.05-noimages/afterstep && rm -rf desktop backgrounds
16) tar zcpvf AfterStep-2.00.05-noimages.tar.gz AfterStep-2.00.05-noimages
17) tar cpvf AfterStep-2.00.05-noimages.tar AfterStep-2.00.05-noimages
18) bzip2 AfterStep-2.00.05-noimages.tar
19) upload tarballs, ChangeLog and NEW files on ftp.afterstep.org
20) upload tarballs on upload.sf.net/incoming/
21) Add file release on Sourceforge.
22) Annonce release on freshmeat.net
23) Annonce release on AS-ML
24) Update wao pages : index.php, download.php and news
25) test release on your own computer
26) realise that you fucked up and go apologise to everybody
27) watch new release not getting propagated into distros and users installing 
    some wierd beta from yer back.
28) realise futulity of it all and go on a drinking binge


