Chapter 19. Making a Release

Table of Contents

Setting version in NEWS file, checking ChangeLog
Tagging the CVS
Building The "Standard" Tarball
Building The "Full" Tarball
Building The Debian Package
Building The RPM Package
Making sure the FreeBSD port gets updated
Uploading The Release
The LogReport Webserver
Advertising The Release
SourceForge
Freshmeat.net

Before making an official Lire™ release, it should have been tested on all supported platforms. A release shouldn't be made unless Lire™ builds, installs and generates an ASCII report from all supported log files on all supported platforms. If this is not the case, the release should be delayed untill this is fixed.

Making a new release of Lire™ involves many steps:

  1. Writing the final version number in NEWS.

  2. Tagging the CVS tree.

  3. Building the "Standard" Lire™ tarball.

  4. Building the "Full" Lire™ tarball.

  5. Building the Debian GNU/Linux™ package.

  6. Building the RPM package.

  7. Making sure the FreeBSD package gets updated.

  8. Uploading the tarballs and making packages available.

  9. Advertising the release.

Setting version in NEWS file, checking ChangeLog

Inbetween releases, the NEWS file generally reads "version in cvs". This should of course be changed to e.g. "version 20011205".

Since August 25, we maintain our ChangeLog file. Make sure the ChangeLog in the toplevel directory is not too big. If needed, split off a chunk and move it to doc/. The ChangeLog is autogenerated from the CVS commits, using the cvs2cl tool. One could e.g. run cvs2cl --prune --stdout -l "-d \>yesterday" -U ../CVSROOT/users.