Week ending March 13th

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

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

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

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

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

• Meta: https://bugzilla.mozilla.org/show_bug.cgi?id=1132944
• Marketing plan happening next week