Hey,

Before going to Whistler (if you are attending), did you forget to complete the survey?

Wesley

Wesley wrote:
Hi folks,

Stealing the thread and hoping get your attention.

I would like to see people's input on suggestions, and pain points during v2.2. 
We want to keep the good things happening, and should never stop improving ourselves.

The survey will probably take less than 5 minutes. Click now.


Note: we’re closing the survey by Thursday.

Cheers,
Wesley

On Jun 9, 2015, at 10:59 PM, Josh Cheng <[email protected]> wrote:

Dear b2g friends,

We are here to announce that we passed 2.2 Code Complete (CC) today Jun 8th. 

=Code Complete Status (As of 6/8 today)=
  • 2.2+ all blockers (Must < 10)
  • MTBF (Must > 100 hrs)
    • Nexus 5: 105 hrs 
  • CAF status
    • Officially reached CS Milestone with the 5/27 build
    • MTBF sustained at 100+ hours 

=Post CC Action Plan= 
  • QA to send V2.2 Daily smoke report - FLAME-KK, NEXUS-5-L and V2.2 Weekly report
  • EPMs will help to continue triage for 2.2 rest blockers.
  • 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. 
We would also like to ask for your feedback of 2.2 retrospective : https://goo.gl/fKsvCy  (Thanks to EPMs!)
Your precious opinion is valuable for continuous improvement to our future release!

Thank you!
-------------------------------------------------------
Josh Cheng
Engineering Project Manager, Firefox OS
Mozilla Corporation
-------------------------------------------------------
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Sent Using Firefox OS
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to