equal
deleted
inserted
replaced
|
1 #summary How releases are done in Hedgewars |
|
2 This page is a checklist of things to do in order to do a proper Hedgewars release. |
|
3 |
|
4 ## Getting ready for release |
|
5 |
|
6 * Bump protocol number |
|
7 * Bump Hedgewars version number (if it hasn't already) |
|
8 * Update `ChangeLog.txt` |
|
9 * Update all translation strings |
|
10 * For the frontend: Run `lupdate ./QTfrontend -ts share/hedgewars/Data/Locale/hedgewars_*.ts` |
|
11 * For Lua: Run `tools/update_lua_locale_files.sh` and grab a coffee |
|
12 * Announce string freeze in News and wait |
|
13 |
|
14 ## Releasing |
|
15 |
|
16 * Add a tag for the relevant commit |
|
17 * Create a Windows build (usually done by unC0Rr) |
|
18 * Update Download page (https://hedgewars.org/download.html) |
|
19 * Announce release on News section on www.hedgewars.org |
|
20 * Announce release in IRC (`#hedgewars`) |
|
21 * Announce release in official server |
|
22 * Update protocol number |
|
23 * Update MOTD |
|
24 * In lobby, use command `/global Hedgewars X.Y.Z has just been released!` (requires server admin rights) |
|
25 * Notify package managers of GNU/Linux distributions |
|
26 |
|
27 ## For release candidates |
|
28 |
|
29 * Create a Windows build |
|
30 * Remember the commit ID to which the release canditate refers to |
|
31 * Write a post in News, you can use this one as a template: https://hedgewars.org/node/6907 |