Firefox3/Schedule/L10n: Difference between revisions

Firefox3/Schedule/L10n (view source)

160 bytes added , 15 May 2007

clarify on B1

Confirmed users, Bureaucrats and Sysops emeriti

2,976

edits

@@ Line 28: / Line 28: @@
 === Proposal ===
-; en-US B1, l10n alpha : The proposal is to freeze en-US on Wednesday, go through QA end of the week, and freeze, tag, repack l10n on the following Monday. We'd alpha any localization that'd be green.
+; en-US B1 (l10n alpha?) : We have two weeks between freeze and shipping of B1. We'll need to evaluate the progress on short notice, but we're currenly not planning to ship B1 with localizations. If progress is looking good and we're not landing too many huge string changes the day we freeze, we'd alpha any localizations that are green, say, mid-freeze.
-; en-US B2, l10n beta : Same proposal as B1, just use the additional week to do dedicated QA
+; String freeze : Two weeks prior to B2 freeze. Tentatively, there could be 6 weeks between B1 ship and B2 freeze, so we'd split that up in two weeks testing, two weeks feature fixing and landing, two weeks of localization.
+; en-US B2, l10n beta : Well frozen, with localized builds for all localizaitons we want to ship.
-With a sufficiently well done l10n swag, we could start to feed localized B1 builds to smartware for 3rd party testing. Smartware testing between B2 and RC1 is possible, but the chance to actually fix bugs found goes down.
 === Alternative Proposal ===
 If we decide that build is much better off with doing both en-US and l10n builds in one go, we would want to freeze the /cvsroot repository for l10n impact changes the Friday before the real freeze Wednesday.