Fennec/NativeUI/BetaReadinessReview

Needed by: May 10-11, 2012

[Erin] Blocking Bug Metrics

Find/Fix rate Blocking Bugs Bounce-Back Rate

[Erin] Deferred Bug Metrics

List the most worrisome bugs that are being deferred. List critical deferred bugs that may have Support impact, or which should be considered for the next beta. Explain why each bug isn't being or can't be fixed.

[Erin] Features Summary

Summarize new features that ship with this release

[Kevin] Test Coverage

1. Summarize the test coverage status for each functional area
2. Please note % level of completion of these items (the goal is assumed to be 100%)
3. Note the number of days required to satisfy the goal of 100% completion. If the goal is not 100% then state the goal

[Naoki]Reliability

1. List the reliability criteria defined for the project
2. State results of reliability testing (measured against the criteria)

[Clint, Wlach, Geoff, Erin] Performance

1. List the performance criteria defined for the project
2. State results of performance testing (measured against the criteria)

[Lukas] Mobile Test Drivers & Usability Testing

1. Number of testers
2. Number of bugs reported
3. Validation (Area of focus and results)
4. Activity (Builds seeded and results)

[AaronMT, Lawrence] Web Compatibility

1. Where we are today
   Investigation is ongoing (crowd sourcing test tool launched 20120508), actively working with select partners to fix site issues.
2. Where we want to be when we ship
   We are working on top sites. Goals are aligned around k9o. Haven't received specific guidance from product about Fennec 1.0 launch.
3. If goals can't be obtained when we ship in June, provide high level for k9o
   High level goals for k9o are captured in bug 747123. Are targeting active involvement with top apps/sites and mitigation strategies for Alexa top sites in specific locales.

[Erin, Alex] Release Plan

1. l10 details <== Erin
2. Google Play Details
   
3. Minimum System Requirements
   <== Erin

[Erin, Eng, QA] Schedule

1. Weekly betas
2. Go-to build dates
3. Google Play release dates
4. We have flexibility until about June 5th

[Jaclyn] Marketing Distribution Plan

List websites being updated/localized/launched for this beta release

• Bug 716029 - https://www.mozilla.org/mobile/beta/ - hero image update
• Bug 727983 - Google Play Store content update

List text (general location is fine) that is being updated and localized)

• Bug 738780 - Localize Google Play Store content

What are the go-live dates for the above

• May 15

Other promos

• Bug 753561 - Facebook ads for messaging testing
• Beta newsletter
• Bug 723184 - Beta channel Snippets
• Reddit IamA campaign

[Erica, Barry] PR & Marketing Intro Plan

1. [EJ]Introduction date, means by which the product will be introduced (press release), notable events, any blog or benchmark requirements from Dev/engineering and due dates
2. [Barry] Any brand marketing activities/website updates planned and dates associated with them

[mluna, Erin, Alex] Support Plan

1. Release notes [alex] https://www.mozilla.org/en-US/mobile/13.0beta/releasenotes/
   
2. [mluna] SUMO
   <== mluna, I believe you and I are meeting about this tomorrow. :)
3. 5/15: en-us support docs complete for Google Play launch; l10n ready
4. http://support.mozilla.org/en-US/mobile#os=android&browser=m14
5. Sync upgrade is the last article to be written
6. firefoxforandroid@mozilla.com: one-time push notification
7. monitor social sites; problem solving on sumo; army of awesome will
8. https://support.mozilla.org/en-US/kb/firefox-mobile-android-tutorials#os=android&browser=m14
9. integrate feedback back into browser- here is the bug we don't think we need this
10. rating reports; low reviews

[All] Issues and Risks

• State any outstanding issues and/or risks