To do for releases
From OpenTTD
Those things have to be done for each release:
Prerelease
- backport all the fixes
- update all release version strings, especially in the following files:
- readme.txt
- docs/openttd.6
- os/debian/changelog (copy-paste-edit)
- os/win32/installer/install.nsi (increment value)
- update the changelog
- sort order: Feature, Codechange, Fix then descending revision number
- format: - (Feature|Codechange|Fix): ([<subsection (like OSX)>])? <message> ([FS#XXX])? (rXXXXX)
- merge items that are solving a single goal
- update the known-bugs.txt
Release
- use 'svn checkout -N svn://svn.openttd.org/tags' to checkout the tags directory without all the files and directories in it (since we only need to add something to it.x)
- create the tag: svn cp svn://svn.openttd.org/branches/<major> <version> (or trunk in case of betas)
- merge standard release changes: svn merge -c 11869 svn://svn.openttd.org/tags/0.6.0-beta3
- replace all instances of 0.6.0-beta3 with the new version and 11869 with the revision that the tag will have (yes a revision in the 'future'); svn diff should not show 0.6.0-beta3 nor 11869 anymore.
- for non-beta/non-RC releases assertions need to be disabled in config.lib and the MSVC project files. Furthermore the 'release' bit needs to be set in rev.cpp.in.
- svn commit -m "-Release <version>"
Post release
- build the binaries and source archives
- source archives
- svn export svn://svn.openttd.org/tags/<version> openttd-<version>
- tar -cf openttd-<version>-source.tar openttd-<version>
- make a gz and a bz2 or this tar
- zip -r ../openttd-<version>-source.zip * (this is ran from within the openttd-<version> directory)
- 32 bits Windows: glx makes them (both a Unicode as a non-Unicode version)
- 64 bits Windows: michi_cc makes them
- Mac OSX: Bjarni makes them
- MorphOS: tokai makes them
- OS/2: orudge still makes them
- Debian 32 and 64 bits packages: blathijs makes them
- Torrent downloads: TrueLight makes them
- source archives
- create a new release at the SourceForge project site
- put a news message on the website and update download locations (i.e. /downloads.php)
- add md5 checksums of binaries to download page
- make a forum announcement
- update the IRC topic
- forwardport/merge the changes made in the prerelease
- for non-RC releases:
- put a message on the SourceForge project site
- update version on FlySpray (current->past, future->current, maybe new future)
- create a wiki page and update the release history
- update wiki pages: Template:Version, Download, FAQ General Questions and Current_events
See also Todo_list
