Confirmed users
1,043
edits
| (24 intermediate revisions by the same user not shown) | |||
| Line 149: | Line 149: | ||
https://groups.google.com/forum/#!topic/mozilla.dev.gaia/5OWAFgdUdcE | https://groups.google.com/forum/#!topic/mozilla.dev.gaia/5OWAFgdUdcE | ||
===Average timeline for | ===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. String Freeze should always appear clearly in all release schedules. Historically, Release Managers always announce it as fully part of the schedule and make regular reminders to make sure everyone remembers and respects this. | |||
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: | ||
* Feature | * '''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. 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. | ||
* | Then follows a cycle during which: | ||
* 2 weeks: QA performs Localization Runs on all languages | |||
* 2 weeks: localizers/devs fix bugs | |||
* 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 | *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: | ||
| Line 175: | Line 182: | ||
** 1st half: April 14 - April 18 | ** 1st half: April 14 - April 18 | ||
** 2nd half: May 12-16 | ** 2nd half: May 12-16 | ||
* v2.0 Localization Run schedule | |||
See [https://www.google.com/calendar/embed?src=ust6tonpqd5fla4okglk2fbfuo%40group.calendar.google.com&ctz=America/New_York| Testing Calendar] | |||
===Scaling Locale Testing=== | ===Scaling Locale Testing=== | ||