Confirmed users
1,043
edits
L10n:B2G/Planning: Difference between revisions
→Average timeline for Localization cycle in FxOS
| (3 intermediate revisions by the same user not shown) | |||
| Line 157: | Line 157: | ||
;Typical calendar within FirefoxOS schedule: | ;Typical calendar within FirefoxOS schedule: | ||
* '''Feature landing''' corresponds to our "'''soft string freeze'''": 80% strings have landed, even though we know some more will come. Developers and Release Managers must use the "late-l10n" keyword in Bugzilla if | * '''Feature landing''' corresponds to our "'''soft string freeze'''": 80% strings have landed, even though we know some more will come. Developers and Release Managers must use the "late-l10n" keyword in Bugzilla if a patch with any kind of string modification is trying to land (ie an addition, an update or a deletion of a string). The late-l10n keyword should be used from this point onwards in the release. Release Management typically starts at this point being more aggressive towards if a feature/patch with a string change should land or not at this point in the cycle | ||
* '''Feature complete''' is our "'''string freeze'''" date: no more strings land or change at that point in the cycle. It is ultimately up to release management if a patch is critical enough that it justifies breaking string freeze and thus can land. It is good to consult with l10n team about this, but we are not the ones who will decide in the end. | * '''Feature complete''' is our "'''string freeze'''" date: no more strings land or change at that point in the cycle. It is ultimately up to release management if a patch is critical enough that it justifies breaking string freeze and thus can land. It is good to consult with l10n team about this, but we are not the ones who will decide in the end. Continue use of "late-l10n" keyword in this phase | ||
* 2 weeks after string freeze: l10n Testing by QA starts. This is the date that we announce to localizers that they should have finished doing their chunk of l10n. | * 2 weeks after string freeze: l10n Testing by QA starts. This is the date that we announce to localizers that they should have finished doing their chunk of l10n. | ||
Then follows a cycle during which: | |||
* 2 weeks: QA performs Localization Runs on all languages | * 2 weeks: QA performs Localization Runs on all languages | ||
* 2 weeks: localizers/devs fix bugs | * 2 weeks: localizers/devs fix bugs | ||