Chapter 12. Making a Release
Prev Part IV. Lire Developers' Conventions Next

Chapter 12. Making a Release

Table of Contents

Setting version in NEWS file
Tagging the CVS
Building The "Standard" Tarball
Building The "Full" Tarball
Building The Debian Package
Building The RPM Package
Uploading The Release
The LogReport Webserver
Advertising The Release
SourceForge
Freshmeat.net

Before making an official Lire release, it should have


Google

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. Uploading the tarballs and making packages available.

  8. Advertising the release.

Setting version in NEWS file

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