Release Management/FirefoxOS/2 2 R Schedule: Difference between revisions

Release Management/FirefoxOS/2 2 R Schedule (view source)

20 bytes added , 5 August 2015

Confirmed users

811

edits

@@ Line 55: / Line 55: @@
 === Feature Complete Criteria ===
 * All feature landing exceptions must be resolved
-* Bugs with keyword late-l10n should be zero
+* [TBD] Bugs with keyword late-l10n should be zero
 * Chipset vendor requirements or bugs needed to meet their FC date must be resolved
 * QA sign-off
 ** Completed one functional test run
-**  QA defines 2 areas of "functional areas" for exploratory testing and lead will send a "signoff" note when he feels its qualitatively ready
+** Mozilla QA defines 2 areas of "functional areas" for exploratory testing and lead will send a "signoff" note when he feels it's qualitatively ready
 ** Smoketest Greenness - Latest length of time that we haven't had smoketest regressions needs to be greater than five days
 ** MTBF Test Run lasts for 30+ hours
 * Perfomance team sign-off to ensure we have met the FC ready criteria
 '''Notes :'''
-* Hard string freeze happens in two weeks as we enter the the FC phase giving the localization team four weeks to localize the strings and prepare for a testrun at FC. FC will typically mark the launch of the initial l10n test run.
+* [TBD] Hard string freeze happens in two weeks as we enter the the FC phase giving the localization team four weeks to localize the strings and prepare for a testrun at FC. FC will typically mark the launch of the initial l10n test run.
 == CODE COMPLETE (CC)==