localizations.rst (1727B)
1 .. role:: bash(code) 2 :language: bash 3 4 .. role:: js(code) 5 :language: javascript 6 7 .. role:: python(code) 8 :language: python 9 10 =========================================== 11 How Migrations Are Run on l10n Repositories 12 =========================================== 13 14 Once a patch including new FTL strings and a migration recipe lands in 15 `mozilla-firefox`, the Localization Team will perform a series of actions to migrate 16 strings for all 100+ localizations: 17 18 - New Fluent strings land in `mozilla-firefox`, together with a migration 19 recipe. 20 - New strings are added to an `update` branch of `firefox-l10n-source`_, 21 a unified repository including strings for all shipping versions of Firefox, 22 and used as a buffer before exposing strings to localizers. 23 - Migration recipes are run against all l10n subfolders, migrating strings 24 from old to new files, and storing them in VCS. 25 - New en-US strings are merged into the `main` branch of `firefox-l10n-source` 26 that syncs with localization tools, exposing strings to all localizers. 27 28 Migration recipes could be run multiple times within a release cycle if more 29 patches containing migrations land after the first. 30 31 Migration recipes are periodically removed from `mozilla-firefox`. This clean-up 32 process will typically leave recipes from the most recent 2 or 3 cycles. Older 33 recipes are stored in `this repository`_ . 34 35 .. tip:: 36 37 A script to run migrations on all l10n repositories is available in `this 38 repository`_, automating part of the steps described for manual testing, and 39 it could be adapted to local testing. 40 41 .. _firefox-l10n-source: https://github.com/mozilla-l10n/firefox-l10n-source/ 42 .. _this repository: https://github.com/flodolo/fluent-migrations