Firefox/2015/4-19
Firefox for iOS, v1.0, Risk Profile= At Risk but within bounds
Risk Profile Change?
No, Yellow for 4 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.
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
- [DONE] Frecency in Top Sites
- Coming: iPad layouts
- Coming: Saving session
- Coming: Frecency in Searches
- In Progress: Fx Sync (Targeting May 1)
- In Progress: Reader View
In Progress: Reading List Sync<== Deferred
Also see this status: https://wiki.mozilla.org/Mobile/Firefox_for_iOS/Status_Report/15-Apr-2015
Next Steps and Go to Green Plan
Reading List Sync needs to be disabled/Backed out. Team continues to work towards string freeze and feature complete by May 1.
Tracking for iOS
80 Total; 2 Open (2.5%); 77 Resolved (96.25%); 1 Verified (1.25%);
Firefox for Android, v38.0.5, Risk Profile = Almost on track
Risk Profile Change?
No, Fennec has been yellow for about 3 weeks.
Why Yellow?
Unclear as to what the user experience with Reading List sync is given change to Desktop; need to ID what the new narrative will be for campaign, given the Pocket Add-On integration for the Home Panels on Android has been shipping for some time, we need to ID what the interaction for Desktop will be if any?
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.
Next Steps and Go to Green Plan
- Remaining work is being tracked via bug 1123101
- Full end-to-end testing with production endpoints for synced Reading List
- Will monitor fix rate vs. incoming bugs as well as regressions and bounce backs
- Healthy balance of the above along with good stability (1.5 crashes or less per 100 ADU) will keep this feature ‘on track’
Tracking for Firefox for Android 38.0.5
| ID | Priority | Summary | Status | Assigned to |
|---|---|---|---|---|
| 1063844 | -- | [onboarding] Start Pane v1.5 | RESOLVED | Chenxia Liu [:liuche] |
| 1082011 | -- | [meta] Create a central Reading List attached to FxA | RESOLVED | |
| 1120004 | -- | Update Reader View controls | RESOLVED | :Margaret Leibovic |
| 1159780 | -- | [meta] Dev Edition 40 | RESOLVED |
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?
Yes, given the change to the plan of record at this stage of the release, this risk profile goes to orange/red.
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
- We have buy-in from Product and Engineering to proceed with Pocket integration for 38.1. Chad has communicated the decision and the reasons why to the larger team. Dolske has filed the meta bug and work is being scoped.
Next Steps and Go to Green Plan
- Disable Reading List and Sync for Reading List in 38.1 bug 1155515
- Determine if current schedule will be enough time for implementation and testing
- There's more and we're meeting on Tuesday to enumerate more details, as there are still many details to cover, here are some initial factoids:
- We're not copying the addon, but writing an implementation of our own
fxa testing for sure, workflow is basically sign in or sign up for fxa -> add to pocket button is functional (is just a cta if you aren't signed in)
- 'add to pocket' button testing from softvision
- no real security issues, public api call, hand off most of the work to pocket
- still talking about letting existing users (email or google accounts) in, vs forcing fxa. fxa will likely be the driver as thats kind of the point of this :)
- l10n testing for what is white listed, might just be en-us for 38.1, pocket has 15 locales so will get to that by 40ish
- fxa load, ~ 250k active users on pocket addon, but could be significantly more due to putting pocket in front of all users. might want to dns throttle similar to hello if it comes to that
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 4 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
- Stay on top of incoming bugs and issues
- Will monitor fix rate vs. incoming bugs as well as regressions and bouncebacks
- 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 Until We Land on a Plan
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
- Aligning with June 2nd date
- iOS debugging is likely out of scope due to App Store
- Perf tooling; WebVR
- 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