Archive:Making a new release

Updating the version and release date

The program version and release date are mentioned in several places. Some other places are also important to check before making a release.

• configure.ac (version)
• CMakeLists.txt (version)
• src/winver.h (version)
• README (version and release date)
• INSTALL (dependencies and their versions)
• NEWS (version, release date and changes)
• data/help/header.txt (version and release date)
• data/help/changes.txt (version, release date and changes)

Making a clean tarball

Authors and packagers should work on making a clean tarball, which has no .svn folders, no Makefiles, no .deps folders, etc... That kind of clean is needed when uploading sources such as for debian, and can be obtained thanks to make dist, with automake.

To test that the distribution compiles and installs with just the files included in the release, make distcheck can be used. However, you should also make sure that it actually runs.

Notifying the package maintainers and websites

Normally first the source and Windows releases are made. After verifying everything works with several people for at least a day, the release will be tagged in Subversion. At that point the release is official and the package maintainers should get started on producing their package.

The following people are responsible for updating their packages:

• Debian - the-me
• Slackware - Platyna
• MacOS X - trapdoor
• Arch Linux - Bjørn Lindeijer

The following people are responsible for updating the respective websites:

• http://freshmeat.net/ - Bjørn Lindeijer
• http://games.linux.sk/ - Bjørn Lindeijer
• http://rpgdx.net/ - Bjørn Lindeijer
• http://happypenguin.org/ - ?
• http://packages.gentoo.org/... - Bjørn Lindeijer emails Games herd