...

This page describe the instructions to

...

:

a) The master resource files (english) from CloudStack Git Repo to Transifex
b) the localization files (L10N resource files) with the latest version from Transifex.

When do this work:

• After each new major release on master branch, to add the N+1 release config and after the creation of the release branch by the release manager: add the transifex config for new L10N resources files must be done(just update the tx/.config file
• Regularly or just before make a minor release, update the translation on the release branch (or master)

Requirements:

• Transifex account
• Transifex client (tx) (go to here)
• CloudStack GitHub clone repository and ability to make a Pull Request

Instructions:

For example, with 4.2 7 branch (some lines must modify if your use another CS version to match with correct version number).

Requirement: if the 4.7 resources files don't exists on Transifex, you must create the resource file (en_US) on Transifex website before follow theses commands:

1/ Update your master git repository

git checkout 4.9 # or use 'master' instead 4.2of '4.9' if you would update the main development branch.
git pull

2/ Create a new temporary branch

git checkout -b updateMsgL10N-update-4.9-20160812

3/ Put into transifex Transifex the latest version of messages.properties

cd tools/transifex/
./sync-transifex-ui.sh upload-source-language CloudStack_UI.42xmessagesproperties49xmessagesproperties

4/ Get the latest L10N resource files from transifex

./sync-transifex-ui.sh download-l10n-languages CloudStack_UI.42xmessagesproperties49xmessagesproperties

5/ Add resource files in your local branch and commit

cd ../..
git add ./client/WEB-INF/classes/resources/*.properties
git commit -m "Update L10N resource files with 4.9 strings from Transifex to repo(20160812)"

6/ Create the patch filePush your local branch on Github to create the pull request.

git push format-patch 4.2 -set-stdoutupstream >origin ~/update_l10n_strings_master.patchL10N-update-4.9-20160812

7/ Final step: apply the patch to master and push it.

...

on Github, create a new pull request (PR) for the release manager team.