Firefox/2015/4-10

Summary

The product pieces of this program are converging and although, overall, the status remains 'At Risk' the areas of concern have remained the same for the last ~2-3 weeks and new or unforeseen issues haven't cropped up. We now have a solid release plan to maximize exposure and testing on 38.0 and 38.1.

Firefox for iOS, v1.0, Risk Profile= At Risk but within bounds

Risk Profile Change?

No, Yellow for 3 weeks in a row since schedule shift.

Why Yellow?

The project will be at a ‘Yellow’ risk level until the very end, as we will be working until the last possible moment to ensure the release is a fully featured as possible for V1. Ensuring quality and market readiness remains primary focus. Seeding the build(s) to a non-Mozillian population for pre-launch feedback has been requested to provide a litmus test; :elan is compiling a list of candidates for :kar to vet. We still need alignment to move forward but making progress nonetheless.

Highlights and Accomplishments

• Build 7 is out (with 25 dogfood ready locales!)
• [DONE] Thumbnails in Top Sites
• [DONE] Sharing from Other Apps
• [DONE] Move favicon usage in UI
• Coming: iPad layouts
• Coming: Saving session
• Coming: Frecency in Top Sites and Searches
• In Progress: Fx Sync
• In Progress Reader View
• In Progress: Reading List Sync
  

Also see this status: https://wiki.mozilla.org/Mobile/Firefox_for_iOS/Status_Report/08-Apr-2015

Next Steps and Go to Green Plan

We are evaluating what the change to the POR costs (backing out Sync'd Reading List) to determine if this is going to change the risk profile positively or negatively. Jenn has provided initial end-game milestones, see them in the 'Schedule and Milestones' section below.

Firefox for Android, v38.0, Risk Profile = Almost on track

Risk Profile Change?

No, not this week. Holding 'yellow' until there's confirmation end-to-end testing is successfully completed. "Nothing Changes for Android" holds true for the engineering experience but we're figuring out what the Pocket integration on Desktop means for Android users.

Why Yellow?

Because although the Reading List/Reader View work has landed, we need to continue to test and evaluate quality. Again, we need to be sure the Pocket integration for Desktop doesn't have unforeseen impact on users.

Highlights and Accomplishments

Key pieces for campaign focus have all been landed, uplifted and are enabled.

Next Steps and Go to Green Plan

1. Remaining work is being tracked via bug 1123101
2. Full end-to-end testing with production endpoints for synced Reading List
3. Will monitor fix rate vs. incoming bugs as well as regressions and bounce backs
4. Healthy balance of the above along with good stability (1.5 crashes or less per 100 ADU) will keep this feature ‘on track’

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

Risk Profile Change?

Yes, given the change to the plan of record (Pocket Integration), this portion of the program is moving from 'Yellow' to 'Orange/Almost Red' due to unknown unknowns.

Why Orange Almost Red?

We're changing the plan of record in a big way with Pocket integration but we don't plan on changing the date. This increases risk by default. Once we have all the work scoped and plan for landing, we'll change the risk profile positively or negatively.

Highlights and Accomplishments

1. 12 open bugs in overall campaign meta bug 1132074 and
2. Cache and revoke oauth tokens bug 1139743 has landed in Nightly and will soon be on Aurora to bake prior to uplifting to beta
3. Perf issues have been found/fixed. There will be ongoing attention to performance and the source of truth for perf-related investigation is bug 1150656

Next Steps and Go to Green Plan

1. Reconcile 2 metas to ensure burn down for the campaign is clear, see bug 1123529 and bug 1132074
2. 'One and Done' Dogfooding to help capture cross platform issues, see the outline [[1]].

Firefox for Desktop, v38.0 - Room Sharing for Hello, Risk Profile = On Track

Risk Profile Change?

No, Hello has been Green or 'On Track' for about 2 weeks

Why Green?

String freeze declared on time. Tab sharing has been uplifted and the feature is ready for end-to end testing, it may shift to Yellow depending upon incoming defect reports

Next Steps

1. Stay on top of incoming bugs and issues
2. Will monitor fix rate vs. incoming bugs as well as regressions and bouncebacks
3. Healthy balance of the above along with good stability will keep this feature ‘on track’

Firefox Developer Edition, v40.0, Risk Profile: At Risk Until We Land on a Plan

Risk Profile Change?

Yes, Fx40 has been in Nightly since 03/30.

Why?

Need to land on intended scope for the campaign

Highlights/Next Steps

1. Aligning with June 2nd date
2. iOS debugging is likely out of scope due to App Store
3. Perf tooling; WebVR
4. Implement changes based on user voice/feedback