Checklist before every release

Make sure the correct version number is used in:
- the upgrade/install script main/install/index.php ($new_version = ...)
- the various readmes, installation guides, ...
- update dokeos.com/doc/installation_guide.html (only on stable releases)

Don't forget to commit the latest language files from DLTT before checking out (export) the cvs code to create the release package. Do not first create the release package from cvs and then add the DLTT, this will cause problems.
Just before doing a SVN export, tag the release (as described in detail in Useful scripts). When branching, first create the branch tag and then immediately a normal tag afterwards. Only with this normal tag can you get back in the future the exact versions of the code that you release now.
When releasing test or alpha versions without working upgrade procedure, disable the upgrade button in the installer.
Update the list of changed files in the release notes (see FAQ)

When creating the code archive, make sure the archive unpacks in a directory which includes the version number. This will help to avoid to overwrite other Dokeos installations when unpacking (See forum)

Update version in www.dokeos.com/version.txt (only on stable releases) - make sure it doesn't contain unnecessary blank spaces