author Wuzzy
Fri, 07 Dec 2018 01:51:53 +0000
changeset 1662 a59c733832f5
parent 1623 d5a96c14bec1
child 1665 244fd94698f2
permissions -rw-r--r--
Releasing: fix typo

#summary How releases are done in Hedgewars
= Releasing Hedgewars =
This page is a checklist of things to do in order to do a proper Hedgewars release.

== Getting ready for release ==

 * Try to announce string freeze in News a few weeks before the planned release to give translators a fair chance
 * Bump [ProtocolNumbers protocol number]
 * Bump Hedgewars version number (if it hasn't already)
 * Update server sources
     * Update newest version
     * Make server aware of new version and new -dev version protocol numbers
     * Update MOTD to reflect version changes
 * Update `ChangeLog.txt`
 * Update all translation strings
     * For frontend (.ts) and Lua (.lua): Run `tools/` and grab a coffee
     * Other files might need manual updating
 * If there was a Shoppa tournament after the previous release: Update prizes
     * Put the names of the top 3 players on the plaques in _ShoppaKing_ and _TrophyRace_
     * Add the names of (at least) the top 3 players in the pool of random names in _Rope-Knocking Challenge_
 * Update system requirements, if neccessary:
     * 1) In the `` file
     * 2) In the Hedgewars homepage:

== Releasing ==

 * Add a tag for the relevant commit
 * Create a Windows build
 * Create torrents
 * Update [ release archive]
 * Update [ Download page]
 * Announce release on News section on []
 * Announce release in IRC (`#hedgewars`)
 * Announce release in official server
     * Update protocol number
     * Update MOTD
     * In lobby, use command `/global Hedgewars X.Y.Z has just been released!`

== Post-release ==

 * Notify package managers of GNU/Linux distributions
 * Update Hedgewars Wiki
 * Update HWKB (esp. because of Lua)
 * Update game info on online game databases, if you have access
 * Add new version to Bugzilla
== For release candidates ==
Release candidates may be released before the actual release for testing. They might be combined with a string freeze.

 * Create a Windows build
 * Remember the commit ID to which the release canditate refers to
 * Write a post in News, you can use this post as a template: []