#summary How releases are done in Hedgewars
= Relasing 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 protocol number
 * Bump Hedgewars version number (if it hasn't already)
 * Update `ChangeLog.txt`
 * Update all translation strings
     * For the frontend: Run `lupdate ./QTfrontend -ts share/hedgewars/Data/Locale/hedgewars_*.ts`
     * For Lua: Run `tools/update_lua_locale_files.sh` and grab a coffee
 * Update prizes for the previous Shoppa tournament, if there was a Shoppa tournament after the previous release
     * Put the top 3 names on the plaques in _ShoppaKing_ and _TrophyRace_
     * Add the names of (at least) the top 3 ranking players in the pool of random names in _Rope-Knocking Challenge_

== Releasing ==

 * Add a tag for the relevant commit
 * Create a Windows build (usually done by unC0Rr)
 * Update [https://hedgewars.org/download.html Download page
 * Announce release on News section on [https://hedgewars.org/ www.hedgewars.org]
 * Announce release in IRC (`#hedgewars`)
 * Announce release in official server (requires server admin rights)
     * Update protocol number
     * Update MOTD
     * In lobby, use command `/global Hedgewars X.Y.Z has just been released!`
 * Notify package managers of GNU/Linux distributions
 
== For release candidates ==
Release candidates may be released before the actual release for testing. 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: [https://hedgewars.org/node/6907]