Confirmed users
1,255
edits
Release Management/FirefoxOS/Release Milestones: Difference between revisions
Release Management/FirefoxOS/Release Milestones (view source)
Revision as of 13:15, 11 April 2018
, 11 April 2018move to Archives
(move to Archives) |
|||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{RELEASE_MANAGEMENT_OBSOLETE}} | |||
== Firefox OS Release Cycle and Repos == | == Firefox OS Release Cycle and Repos == | ||
[[File:Firefox_OS_Release.png|800px|centre]] | [[File:Firefox_OS_Release.png|800px|centre]] | ||
<small>Note: Since 2.2, we already increase FL period to 12 weeks. This graphic has to be updated.</small> | |||
A comparison of Firefox and Firefox OS trains: | A comparison of Firefox and Firefox OS trains: | ||
| Line 59: | Line 61: | ||
** QA defines 2 areas of "functional areas" for exploratory testing and lead will send a "signoff" note when he feels its qualitatively ready | ** QA defines 2 areas of "functional areas" for exploratory testing and lead will send a "signoff" note when he feels its qualitatively ready | ||
** Smoketest Greenness - Latest length of time that we haven't had smoketest regressions needs to be greater than five days | ** 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 | * Perfomance team sign-off to ensure we have met the FC ready criteria | ||
'''Notes :''' | '''Notes :''' | ||
| Line 67: | Line 70: | ||
=== Code Complete Criteria === | === Code Complete Criteria === | ||
* No open issues across all user stories | * No open issues across all user stories | ||
* | * Less than 10 valid release blockers. (Additional blockers may be accepted from IOT/certification testing.) | ||
* | * Achieve major chip-set vendor CS milestone. | ||
* Full QA sign-off | * Full QA sign-off | ||
** Target 3 test runs (2 min, 3 max) | ** Target 3 test runs (2 min, 3 max) | ||
** Final test run should >= 98% test case completion | ** Final test run should >= 98% test case completion | ||
** Test failure % is trending downwards at a healthy level (ie. in 1.3, TR1 = 11%, TR2 = 8%, TR3 = 6%) | ** 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. | ** 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. | ** QA defines 4-5 areas of “functional areas” for exploratory testing and lead will send a “signoff” note when he feels its qualitatively ready. | ||
* Sign-off from security, stability, performance | ** MTBF test run lasts for 100+ hours | ||
* Sign-off from security, stability(MTBF), performance, product | |||
* Support documentation published | * 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) == | == General Availability (GA) == | ||
| Line 94: | Line 96: | ||
[[category: | [[category:RelManArchive|FxOS/Cross_Functional/Meetings]] | ||