Release Management/FirefoxOS/Release Milestones: Difference between revisions

[l10n team] Adding informations for the string change part
([l10n team] Adding informations for the string change part)
Line 43: Line 43:
* String Freeze is targeted for two weeks after FL. <code>late-l10n</code> tagged bugs may land in this two week period. There should be no additional string changes after String Freeze has been declared.
* String Freeze is targeted for two weeks after FL. <code>late-l10n</code> tagged bugs may land in this two week period. There should be no additional string changes after String Freeze has been declared.
* Options if you find that string changes are required after String Freeze:
* Options if you find that string changes are required after String Freeze:
** Land string changes before the String Freeze date and complete your work after the String Freeze date.
** If you have to land minor polish fixes for your feature, land string changes before the String Freeze date and complete your work after the String Freeze date.
**  Reuse existing strings in the product instead of adding new ones.  
**  Reuse existing strings in the product instead of adding new ones.
*** Note: Text may be translated differently based on context. Ensure that the strings that you are to use fit in the context.
*** This should be done only after having consulted the l10n team, see [https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_best_practices#Don%27t_reuse_strings_in_different_contexts why it is tricky to reuse strings]
*** Seek the l10n team's advice as needed.
** If you need to make a string change after the String Freeze date, speak with release management and l10n about options.
** If you need to make a string change after the String Freeze date, speak with release management and l10n about options.


Confirmed users
111

edits