| | 34 | == Announce string freeze |
| | 35 | '''Description:''' [[BR]] |
| | 36 | Translators should be informed about the planned String freeze date and the Translation freeze date. The idea is to give them some time to polish the final translations for the release. During development, they probably don't always update translation within a few days after something has changed. Also upload updated .pot files and make sure you update them if original strings change or get added in the next days. |
| | 37 | [[BR]]'''Can be completed in phase:''' Development |
| | 38 | [[BR]]'''Candidates:''' Gallaecio, Leper, Sanderd17, Yves |
| | 39 | |
| | 40 | == Organize staff match (testing) |
| | 41 | '''Description:''' [[BR]] |
| | 42 | If possible a staff match should be organized before the release. Often important bugs get discovered in such staff matches. Organizing the match means finding a good date and time and informing the other team members (or community members). |
| | 43 | [[BR]]'''Can be completed in phase:''' Development |
| | 44 | [[BR]]'''Candidates:''' Whole team |
| | 45 | |
| | 46 | == Confirm translation freeze |
| | 47 | '''Description:''' [[BR]] You make another announcement on the translation platform at the specified and announced Translation freeze date (assuming it hasn't changed in the meantime). After that, you regenerate the translation templates via [source:ps/trunk/source/tools/i18n/updateTemplates.py updateTemplates.py] and the translations (for backup purposes) via [source:ps/trunk/source/tools/i18n/pullTranslations.py pullTranslations.py]. |
| | 48 | [[BR]]'''Can be completed in phase:''' Translation freeze |
| | 49 | [[BR]]'''Candidates:''' Gallaecio, Leper, Sanderd17, Yves |
| | 50 | |
| | 51 | == Translation check |
| | 52 | '''Description:''' [[BR]] |
| | 53 | Check the translations for "vandalism". It's really just checking if there are any strings that were added in bad intent and not about trying to improve translation quality. There's a script to check the translation files for URLs (TODO: where?), but this task also involves manual checking. Obviously we can't carefully read through all strings in all translations. |
| | 54 | [[BR]]'''Can be completed in phase:''' Translation freeze |
| | 55 | [[BR]]'''Candidates:''' Whole team |
| | 56 | |
| | 57 | == Multiplayer lobby adjustments |
| | 58 | '''Description''' [[BR]] |
| | 59 | * Change the MUC room for the lobby on the server and maybe reset rankings. |
| | 60 | * Change the bot's welcome message to notify users that a new version is available. |
| | 61 | [[BR]]'''Can be completed in phase:''' ??? |
| | 62 | [[BR]]'''Candidates:''' Leper, Josh, Scythetwirler |
| | 63 | |
| | 64 | == Prepare for packaging |
| | 65 | '''Description''' [[BR]] |
| | 66 | * Ensure Alpha name and number have been updated in [source:ps/trunk/binaries/data/mods/public/gui/session//top_panel/label.xml label.xml], [source:ps/trunk/binaries/data/mods/public/gui/pregame/mainmenu.xml mainmenu.xml], and [source:ps/trunk/source/lobby/XmppClient.cpp#L107 XmppClient.cpp]. |
| | 67 | * Edit the [source:/ps/trunk/source/tools/dist/build.sh build.sh] script to include all languages that need to be in the release (Include only >90% languages supported by our fonts and font system - see progress [https://www.transifex.com/projects/p/0ad/ on Transifex]) |
| | 68 | * Change the MUC room for the lobby in [source:ps/trunk/binaries/data/config/default.cfg default.cfg] |
| | 69 | [[BR]]'''Can be completed in phase:''' ??? |
| | 70 | [[BR]]'''Candidates:''' Whole team |
| | 71 | |
| | 72 | |
| | 73 | |
