...
Cadence
Weekly release strings are usually done every week, on Thursday morning (Ned Batchelder (Deactivated)).
2. Pulling Translations
How to pull weekly translations (Anyone can do this; I believe you need a transifex account and a .transifexrc file (leave the "token" field blank), but no other special permissions are required):
- paver i18n_robot_pull
Commit the translations, make a PR, and merge it; see https://github.com/edx/edx-platform/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aclosed+update+translations+(autogenerated+message) for past PRs to see what they look like.
See also: Automatically updating resource files in Transifex
3. Pushing Translations
Process
Uses paver commands and manually created PRs
- In your edx-platform working tree, start a branch:
No Format git checkout -b you/update_translations
- In your devstack, run a paver command:
No Format paver i18n_robot_pull- Takes a while (30-40 min?)
- If there are problems, will create .prob files
- Read those files and fix the strings
- You can fix a string by editing it on Transifex to have the right placeholders (the usual problem)
- Or you can unreview a string and ping the translator to come and fix it.
- Once strings are fixed on Transifex, you have to run the paver command again (ugh, takes a long time)
- Read those files and fix the strings
- At the end, it asks if you want to commit the changes, say yes (probably makes sense to automate away this manual step)
- In edx-platform, make a pull request
No Format git push -u origin you/update_translations- (make a pull request however you like to do that)
- The tests will run. Once they are done, you can merge the PR
- In your devstack, run another paver command:
No Format paver i18n_robot_push- Pretty fast (1 min?)
Only someone with Transifex admin permissions can do this, currently Ned and Andy Armstrong (Deactivated). Again youYou'll need a .transifexrc file.
...
See also: Automatically updating resource files in Transifex
Which strings will be used?
In Transifex strings have three states:
...