equal
deleted
inserted
replaced
8 * Bump Hedgewars version number (if it hasn't already) |
8 * Bump Hedgewars version number (if it hasn't already) |
9 * Update `ChangeLog.txt` |
9 * Update `ChangeLog.txt` |
10 * Update all translation strings |
10 * Update all translation strings |
11 * For the frontend: Run `lupdate ./QTfrontend -ts share/hedgewars/Data/Locale/hedgewars_*.ts` |
11 * For the frontend: Run `lupdate ./QTfrontend -ts share/hedgewars/Data/Locale/hedgewars_*.ts` |
12 * For Lua: Run `tools/update_lua_locale_files.sh` and grab a coffee |
12 * For Lua: Run `tools/update_lua_locale_files.sh` and grab a coffee |
13 * Announce string freeze in News and wait |
13 * Announce string freeze in News a few weeks before release to give translators a fair chance |
14 |
14 |
15 == Releasing == |
15 == Releasing == |
16 |
16 |
17 * Add a tag for the relevant commit |
17 * Add a tag for the relevant commit |
18 * Create a Windows build (usually done by unC0Rr) |
18 * Create a Windows build (usually done by unC0Rr) |
24 * Update MOTD |
24 * Update MOTD |
25 * In lobby, use command `/global Hedgewars X.Y.Z has just been released!` (requires server admin rights) |
25 * In lobby, use command `/global Hedgewars X.Y.Z has just been released!` (requires server admin rights) |
26 * Notify package managers of GNU/Linux distributions |
26 * Notify package managers of GNU/Linux distributions |
27 |
27 |
28 == For release candidates == |
28 == For release candidates == |
|
29 Release candidates may be released before the actual release for testing. Might be combined with a string freeze |
29 |
30 |
30 * Create a Windows build |
31 * Create a Windows build |
31 * Remember the commit ID to which the release canditate refers to |
32 * Remember the commit ID to which the release canditate refers to |
32 * Write a post in News, you can use this one as a template: https://hedgewars.org/node/6907 |
33 * Write a post in News, you can use this one as a template: https://hedgewars.org/node/6907 |