Firefox/2015/4-27

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

Risk Profile Change?

No, Fennec has been yellow for about 4 weeks.

Why Yellow?

We now have clarity as to what the user experience with Reading List sync is given change to Desktop (see below) but this project remains in an 'At Risk' state by default.

Highlights and Accomplishments

We have consensus there will be no change to the plan of record for Android. Testing will continue as usual but the Desktop use-case will be removed for now, here is the play-by-play:

1. Reading List will ship except now without Sync
2. Margaret is working to revamp the Pocket Panel, called "Pocket Hits" not 100% sure it will be ready (Pocket for Home Panels has been shipping in Android for quite some time)
3. The above Pocket Panel is *not* a web view it won’t be linked to accounts automatically. Nor will the the panel be connected to Reader View

Next Steps and Go to Green Plan

1. Go/No-Go on refreshed Pocket Home Panel (need to ID a date for this)

Tracking for Firefox for Android 38.0.5

4 Total; 0 Open (0%); 4 Resolved (100%); 0 Verified (0%);

Firefox for Desktop, v38.0.5 - Pocket Integration and Reader View Risk Profile = High Risk

Risk Profile Change?

No, we've been orange/red for 1 week since deciding upon changes to integrate Pocket.

Why Orange/Red?

Until we have a more provable scenario with basic implementation, we'll be in the 'high risk' category, especially given we have 6 weeks left in the project . . .

Highlights and Accomplishments

Pocket

Heroic level of work complete last week on part of the team tackling Pocket work, we are within striking distance of the goal to have a proto by Wed 04/29. Until everything lands, we're day-for day but the team is doing awesome:

1. R+'d patch queue pushed to FxTeam and is green; looks like we still need an icon but really good progress on initial implementation: bug 1155523 - Implement Pocket toolbar button
2. R+'d Patch: bug 1156878 - Send a request to the server when clicking the Pocket toolbar button, not pushed yet
3. Bryan reports they worked out an offline (or poor network) solution that can be supported given the time left. Rather than retrying automatically, user will be prompted to manually re-try
4. Bryan also reports that migration of existing users, legacy add-on and social api the Social API Pocket service will be remove and users migrated to the Fx integration, the legacy add-on will remain and will hide the v1 integration, and in a v2 release of the Pocket integration Pocket will deprecate their add-on to migrate users over

ALSO: Brand Engagement finalized the existing copy for their campaign elements to remove Reading List and instead refer to Pocket. A meeting regarding Pocket promotion is happening this Wed.

Reader View and Readability.js

Given all the Pocket conversation, we shouldn't forget about Reader View which is super important; team continues to chip away.

1. bug 1154028 - Make sure reader view UI styles don't accidentally get applied to readability content (landed in Fxteam, not sure about plan for uplift)
2. bug 1158184 - Week 17 / April 24 - -Uplift github version of Readability/JSDOMParser into mozilla-central and aurora/beta (landed in FxTeam, uplift requested)
3. Thorough break-down bug of Reader View changes for desktop to better tune for Pocket's look and feel: bug 1155536 - [breakdown] Tune Reader View style to better match Pocket's reader view

Next Steps and Go to Green Plan

1. [DONE] Disable Reading List and Sync for Reading List in 38.1 bug 1155515
2. 04/29 Determine if current schedule will be enough time for implementation and testing
3. 05/13 Final 'GO/No-GO'
4. Working to finalize strings for panels (Friday was the goal)
5. Need to determine if there is time for First Run/UI Tour
6. Brand engagement is determining plan for promoting Pocket this week

Tracking for Pocket

91 Total; 13 Open (14.29%); 55 Resolved (60.44%); 23 Verified (25.27%);

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

Risk Profile Change?

No, Hello has been Green or 'On Track' for about 5 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’

Tracking for Hello

3 Total; 0 Open (0%); 3 Resolved (100%); 0 Verified (0%);

Firefox Developer Edition, v40.0, Risk Profile: 'At Risk'

Risk Profile Change?

No, Fx40 has been 'yellow' since it was merged to 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

Tracking Dev Edition

• Need to triage meta:
• Team has also dividing and conquering this list http://mzl.la/1HVvrjf
• Stay tuned for an update this week