Release Management/FirefoxOS/Release Milestones: Difference between revisions

Release Management/FirefoxOS/Release Milestones (view source)

53 bytes removed , 10 June 2015

Confirmed users

811

edits

@@ Line 68: / Line 68: @@
 === Code Complete Criteria ===
 * No open issues across all user stories
-* Zero mozilla driven blockers. (Additional blockers may be accepted from IOT/certification testing.)
+* Less than 10 valid release blockers. (Additional blockers may be accepted from IOT/certification testing.)
-* Zero chipset vendor driven blockers.
+* Achieve major chip-set vendor CS milestone.
-* Chipset vendor sign-off for OEM/ODM to begin testing
 * Full QA sign-off
 ** Target 3 test runs  (2 min, 3 max)
 ** Final test run should >= 98% test case completion
-** Final test run targets <= 10 valid blockers
 ** Test failure % is trending downwards at a healthy level (ie. in 1.3, TR1 = 11%, TR2 = 8%, TR3 = 6%)
 ** Smoketest Greenness - Latest length of time that we haven't had smoketest regressions needs to be greater than five days.
 ** QA defines 4-5 areas of “functional areas” for exploratory testing and lead will send a “signoff” note when he feels its qualitatively ready.
 ** MTBF test run lasts for 100+ hours
-* Sign-off from security, stability, performance, marketplace, content, product, SUMO
+* Sign-off from security, stability(MTBF), performance, product
 * Support documentation published
-* Release notes completed and ready to publish
+* [https://developer.mozilla.org/en-US/Firefox_OS/Releases Release notes] completed and ready to publish
 == General Availability (GA) ==