Dear b2g friends, I am here to announce that we passed 2.2 Feature Complete (FC) today Apr 29 and we are moving forward to Code Complete (CC) milestone targeting June 8th. We will have a 2.2 CC quality review meeting 1 or 2 weeks before CC. Please check the following FC assessment and CC schedule / milestone / plan.
=Feature Complete Criteria Assessment (As of 4/29 today)= All feature landing exceptions must be resolved feature-b2g: 0 bugs, http://mzl.la/1zeXs6h <http://mzl.la/1zeXs6h> blocking-b2g: 44 bugs, http://mzl.la/1A5MLxF <http://mzl.la/1A5MLxF> Bugs with keyword late-l10n should be zero Yes, http://mzl.la/1Gp2XMx <http://mzl.la/1Gp2XMx> Chipset vendor requirements or bugs needed to meet their FC date (May 8th) must be resolved CAF FC, 8 bugs blocking-b2g 2.2 not met http://mzl.la/1bDGbID <http://mzl.la/1bDGbID>. 7 with owners, please help to fix them! Completed one functional test run Yes, 2 runs. QA defines 2 areas of "functional areas" for exploratory testing and lead will send a "signoff" note when he feels its qualitatively ready - Yes. Smoketest Greenness - Latest length of time that we haven't had smoketest regressions needs to be greater than five days OTA issue http://mzl.la/1InuGly <http://mzl.la/1InuGly> is not yet resolved but almost fix. MTBF Test Run lasts for 30+ hours: NEXUS-5-L 5.1 PVT build MTBF 24.4 hrs. http://bit.ly/1DM23ce <http://bit.ly/1DM23ce> Blocked by Bug 1155490 - [MTBF][Nexus5-L][Camera] Crash at android::AudioSystem::get_audio_flinger <https://bugzilla.mozilla.org/show_bug.cgi?id=1155490>. Becker is helping to fix it. FLAME-KK 4.4 PVT build MTBF 34.42 hrs. http://bit.ly/1Q1fzR2 <http://bit.ly/1Q1fzR2> =CC Schedule / Milestone / Plan= v2.2 passed FC milestone and next milestone is CC targeting June / 8th. 44 blocking-b2g including 8 CAF blocker bugs, http://mzl.la/1A5MLxF <http://mzl.la/1A5MLxF>, Please kindly help to resolve them asap. Any non-blocking bugs, need to go through approval process. [1] QA to focus on exploratory test, regression test, and MTBF. A bug will only land in v2.2 if it is marked with blocking-b2g:2.2+ or the patch has gotten an exception through either approval-mozilla-b2g37+ (Gecko) or approval-gaia-v2.2+ (Gaia). Gaia approval requests will not be encouraged after 5/25 and the bar to approve bugs will get higher as we get towards the end of stabilization. Any 2.1 / 2.0 landing that breaks QA smoketests needs to go through approval process to get it landed the second time on 2.1 / 2.0 branch. This applies to blocking-b2g:2.1+, blocking-b2g:2.0+ bugs as well. =Resources= Per team blockers : http://charts.mozilla.org/fxos/blockers.html#project=1.3T,1.4,2.0,2.1,2.2 <http://charts.mozilla.org/fxos/blockers.html#project=1.3T,1.4,2.0,2.1,2.2> CC criteria: http://mzl.la/1J7RrYS <http://mzl.la/1J7RrYS> Branch/Landing information : https://wiki.mozilla.org/Release_Management/B2G_Landing <https://wiki.mozilla.org/Release_Management/B2G_Landing> [1] Uplift Guidelines : https://wiki.mozilla.org/Release_Management/Uplift_rules#General <https://wiki.mozilla.org/Release_Management/Uplift_rules#General> https://wiki.mozilla.org/RapidRelease/Calendar <https://wiki.mozilla.org/RapidRelease/Calendar> Triage times and queries : https://wiki.mozilla.org/B2G/Triage#Triage_for_2.2.0 <https://wiki.mozilla.org/B2G/Triage#Triage_for_2.2.0> [email protected] <mailto:[email protected]>, if you have a question or a bug you've nominated isn't getting the attention it deserves Sincerely, ------------------------------------------------------- Josh Cheng Engineering Project Manager, Firefox OS Mozilla Corporation ✉ [email protected] <mailto:[email protected]> -------------------------------------------------------
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
