Firefox/2015/4-3

General

This project remains at risk even though we have extended the schedule. iOS Build 6 is out and is garnering solid feedback, otherwise, the team is sprinting to to be feature complete by May 1st. l10n build availability also needs to be resolved. Granular End-Game plan identifying dates, tasks, and owners for iOS is due April 8th.For 38.1, Sync'd RL/RV continues to be critical path. Testing is ramping up and we've hit convergence as of last Friday as of the first Nightly-Nightly testing. Dogfooding using 'One and Done' for RL/RV is kicking off this week.

Next Decision needed

Need to land on plan for beta and GA releases for 38.1. Proposal is currently being considered and we're working toward consensus by end of upcoming week.

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

Risk Profile Change?

No, Yellow for 2 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. Top issues include sync risk, l10n builds and a crisp plan for End-Game.

Highlights and Accomplishments

• Build 6 survey is out
• [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: Reading List Sync

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

Next Steps and Go to Green Plan

1. Considering Sync'd Reading List 'At Risk' until it lands and we have a sense of how it's working
2. Need to reconcile l10 builds asap
3. Due by April 8: granular timeline for End Game to be sure we have all cross-functional activities straight.

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

Risk Profile Change?

Yes, Fennec went to straight up yellow because although uplifts are now complete, End-to-end for Android<->Android and Desktop<->Android will happen as of Beta 2 which will GTB on 04/06 and due to release one 04/09.

Why Yellow?

Sync wasn't enabled by default for Reading List and Reader View; should be by Beta 4.

Highlights and Accomplishments

Key pieces for campaign focus have all been landed, but currently turned off. Production endpoints are now available for connected reading list, so we will be turning this on in nightly this week to get a feel for how it is functioning. It will NOT be turned on in Beta 1 to give it some time to bake, but is instead targeted to be functional for Beta 2

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 = At risk

Risk Profile Change?

No, this is the second week in a row it has been yellow.

Why Yellow?

While the team has been consistently adding new work the pace of completion has been high enough to decrease the total backlog size with each iteration.That said, large introductions of new work will need to cease as development approaches the final iteration end date.The team will need this slack to accommodate the introduction of defects discovered by QA as testing progresses.The constant addition of new work also places an additional burden on QA to catch up with this influx and provide defect verification. End-to-end testing will continue next week. The risk profile will shift either positively or negatively based upon testing (and resulting convergence).

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