Confirmed users
1,043
edits
L10n:B2G/Planning: Difference between revisions
→Average timeline for Localization cycle in FxOS
| Line 151: | Line 151: | ||
===Average timeline for Localization cycle in FxOS === | ===Average timeline for Localization cycle in FxOS === | ||
The entire localization cycle has been estimated to last approximately 8 weeks starting at String Freeze date. String Freeze is when no more features are landing, and no patches with string modification land (ie no more adding, modifying, taking out strings in patches). Thus, String freeze usually corresponds to Feature Complete (FC), the later being determined by Release Management. | The entire localization cycle has been estimated to last approximately 8 weeks starting at String Freeze date. String Freeze is when no more features are landing, and no patches with string modification land (ie no more adding, modifying, taking out strings in patches). Thus, String freeze usually corresponds to Feature Complete (FC), the later being determined by Release Management. | ||
Translating work for most teams starts at string freeze, and localizers have then 2 weeks to catch up with their work before QA starts. 2 weeks after string freeze, QA starts doing Localization Runs on all available languages. | Translating work for most teams starts at string freeze, and localizers have then 2 weeks to catch up with their work before QA starts. 2 weeks after string freeze, QA starts doing Localization Runs on all available languages. | ||
;Typical calendar within FirefoxOS schedule: | ;Typical calendar within FirefoxOS schedule: | ||
| Line 161: | Line 163: | ||
* 2 weeks: localizers/devs fix bugs | * 2 weeks: localizers/devs fix bugs | ||
* 2 weeks: QA/localizers verify that all issues are fixed | * 2 weeks: QA/localizers verify that all issues are fixed | ||
;Concerning l10n testing for ONE locale, and assuming there are at least eight full-time testers on a locale, we have identified | ;Concerning l10n testing for ONE locale, and assuming there are at least eight full-time testers on a locale, we have identified | ||
*3 days for one full localization run on one locale, bug filing, etc (full time) | *3 days for one full localization run on one locale, bug filing, etc (full time) | ||
;Average number of bugs that turn up with this kind of testing: | ;Average number of bugs that turn up with this kind of testing: | ||