ReleasingWesnoth
From The Battle for Wesnoth Wiki
- dos2unix text-files
- pngcrush .png-files to hopefully reduce size
- Update Manual (from Wiki?)
- Update version and 'default server' in configure.ac, src/wesconfig.h and config.h.dummy
- Update VC++ project files (Sirp?)
- Commit changes
- Make release tag in CVS
- Do fresh checkout with tag and create release tarball ('make dist')
- Build wesnoth from release tarball (--enable-server --enable-editor --enable-tools --enable-campaign-server)
- Make md5sum of the release tarball
- (I have signed md5sum with gpg, so tarball can be matched against md5sum and md5sum can be verified with gpg, just in
case there is even reason to check if tarball(s) have been tampered)
- Upload release tarball and md5sums to ftp.wesnoth.org/www/files/ and SourceForge
- Post release announcement to forum
- Update Wesnoth web-site: news, downloads
- Inform binary builders, packagers and porters (see WesnothBinaries)
- Announce
- Other sites that follow our releases