Things to do in order to make a new release: 

- Get the latest cvs sources

- Update and commit the following files:
  * ChangeLog
  * NEWS

- Update the version string in configure.in 

- run 
  $ rm -rf tmpdist && ./autogen.sh && ./configure && make dist' 
  to create a tarball

- Open the tarball in a new directory
  * Check that it compiles cleanly
  * Check that it passes the tests

- gpg sign the tarball. 

  to sign: gpg -a -b file_name_here
  to verify: gpg --verify signature_file_here

- Upload the tarball to sourceforge, using the file release system.

- Download it and compare md5sums with the local copy. 

- Tag the cvs sources as 'release r_0_foo'

- Write a release anouncement, using the 'release-announcement'
  template found in this directory. Make sure to update it for the
  current release!

- Announce the release on relevant mailing lists and websites -

  syscalltrack-hackers, 
  freshmeat, 
  linux-il, 
  lin-club, 
  linux-kernel, 
  the project's webpage 
  the project's project page. 

  The email subject should be e.g. "ANN: syscalltrack v0.72 "bald
  hare" released"
-- 
mulix
