Difference between revisions of "ReleasingWesnoth"
From The Battle for Wesnoth Wiki
(BeOS builder has been AWOL since 2004) |
(Categorize) |
||
| Line 1: | Line 1: | ||
| + | {{Needs update}} | ||
| + | |||
| + | Hey, Ivanovic...the list of binary-builders for non-Linux platforms needs to be fixed. | ||
| + | |||
* dos2unix text-files | * dos2unix text-files | ||
* pngcrush .png-files to hopefully reduce size | * pngcrush .png-files to hopefully reduce size | ||
Revision as of 09:13, 25 February 2008
Attention: This page has been marked for review for version 1.4. The information contained here appears to be outdated or obsolete.
If you can, please take the time to review and edit it to bring it up to date (if needed) for the lastest version of Wesnoth. For more information and discussion, check the appropriate thread in the fora.
Once this is done, remove this notice
Hey, Ivanovic...the list of binary-builders for non-Linux platforms needs to be fixed.
- 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)
- Windows builder (Sirp)
- MacOSX builder (Sithrandel)
- Announce
- Other sites that follow our releases