Firefox/2015

From MozillaWiki
Jump to navigation Jump to search

Firefox Q2/Q3 Growth Campaign

Objectives

  • Continue to establish Firefox as the browser of choice for independents on the web
  • Acquire new Firefox users globally across desktop and mobile - with particular focus on North America - in the first 6 weeks post launch
  • Launch Firefox iOS to demonstrate increased commitment to mobile
  • Show a connected Firefox experience demonstrated though a connected Reading List feature across Desktop, Android and iOS.
  • Expand user expectations of Firefox with Hello, made more useful with screen sharing functionality

Release Schedule and Milestones

See the weekly Engagement Team calendar, here.
Release Train Schedule for Reference

March 16: Product String Freeze
<== status March 16-20: Reading List/Reader View engineering work week in SFO
'March 25: Go/No-Go for all features in preparation for marketing/web string freeze
April 6: Marketing and web string freeze
April 8: Quality check point
April 20: SUMO article(s) ‘OK to translate’ to L10n
May 4: Release Candidate Go To Build
May 8: OTR’s (OK to Release) Due from QE
May 12: GO LIVE

Status Week Ending March 13th

Firefox for iOS, v1.0, Risk Profile= At Risk

FxiOSRisk0313.png
Why at risk? Although the team has made significant progress and has successfully built basic browsing and search functionality, current scope of features targeted for v1.0 release is too large given current resources and condensed schedule. String freeze date is pending; goal to identify one by 03/18.
Go to Green Plan = Triage and scrub to identify ‘must-haves’ for MVP is underway and we should have a re-calibrated plan next week. Dogfooding program which launched in Feb will continue with to augment quality testing and provide valuable real-world feedback.
Read Full Status and access lot’s of great information, here: https://wiki.mozilla.org/Mobile/Firefox_for_iOS/Status_Report/11-Mar-2015

Firefox for Android, v38.0, Risk Profile = At risk but almost on track

FennecRisk0313.png
Why? Reading List and Reader View require changes and enhancements to currently shipping features and workflows so although work is significant, there are less unknowns. #1 Dependency is production end-points for server which is targeted for March 16th. Next milestone is string freeze = March 16th which is on track. More information on feature test plan will be available next week. See Meta bug, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1132054

Firefox for Desktop, v38.0 - Reading List and Reader View Risk Profile = At risk

ReadingListReaderViewRisk0313.png

Why at risk? There are three main areas of risk. (1) The readability.js code used for reader view has a number of performance and rendering/display issues (on many pages the reader view is missing important content, rearranges parts of text, or has otherwise poor results). (2) The reading list sync engine is still being implemented, leaving little time for bug fixes and end-to-end testing. (3) General risk from having lots of work to do, with no slack to address new issues/bugs that may arise. This includes the potential for needing to change pre-landed strings as the code using them is implemented.Unlike previous projects on accelerated schedules, we have large amounts of complex new and/or untested code landing very close to release, which need to coordinate across multiple products. This multiplies risk across the board, and makes it more likely unknown issues will be found that we can not address in time.
Go to green plan = We are gathering the team in SF on 3/16 for a meet up, and are trimming down features where possible (although there is not a lot to cut). Specifically for readability.js, we have a plan to avoid the performance issues entirely and will be attempting to improve readability.js as much as we can before shipping. Some Android and server testing will occur until the desktop sync engine is ready.

Firefox for Desktop, v38.0 - Room Sharing for Hello, Risk Profile = At risk but almost on track

HelloRisk0313.png
Why? Windows sharing landed, Tab sharing on track for March 16th - uplift to Fx38 on track. SDK was patched and we are fixing a few last bugs to uplift into 38. Share tabs and share windows are currently in progress. Once that has landed, things will be greener.
See UX, here: https://projects.invisionapp.com/share/GU1Z0XTXR#/screens

Firefox Developer Edition, v40.0, Risk Profile = No risk profile, yet. Ramping up, Fx40 will be Nightly as of 03/30 which will trigger Red/Yellow/Green status

DevEdition.png

Tracking

Full Query
ID Priority Summary Status Assigned to
1128338 -- [Meta] [engagement] Web elements for Firefox Q2 Growth Campaign (2015) RESOLVED
1132054 -- [META] Fennec 38 (for campaign tracking) RESOLVED
1132074 -- [Meta] Desktop - Firefox Q2 Growth Campaign NEW
1132581 -- [Meta] Loop - Firefox Q2 Growth Campaign RESOLVED
1132944 -- [Meta] Developer Tools features for Q2 Growth Campaign RESOLVED
1141844 -- [Meta] SUMO content for Firefox Growth Campaign 2015 RESOLVED Joni Chan
1155467 -- [meta] Firefox Pocket integration RESOLVED
1159780 -- [meta] Dev Edition 40 RESOLVED

8 Total; 1 Open (12.5%); 7 Resolved (87.5%); 0 Verified (0%);


Quality Test Plans

WIP

Communication

  • #planning
  • Weekly Meetups @ 9AM Pacific Every Wednesday, Vidyo = Program Management