- 1 e10s Weekly Update: Feb 8
- 1.1 Executive Summary
- 1.2 Why yellow? e10s is designated 'yellow' or 'at risk' because:
- 1.3 Highlights and Accomplishments
- 1.4 Next Steps
- 1.5 Validation for Stability and Performance
- 1.6 Add-Ons + WebExtensions
- 1.7 Automated tests
- 1.8 A11y
- 1.9 Release Schedule
- 1.10 Milestones
e10s Weekly Update: Feb 8
- The Plan of record is to enable e10s as of Firefox 46 (GA April 19). This initial GA release will be a cohort release targeting 100% of users without Add-Ons, users without a11y features enabled, and, the non-RTL language versions of Firefox.
- The team is currently focused on burning down Milestone 8 issues. M8 tickets block riding the trains for the above populations as of 46 Beta (March 8). M8 is largely focused on correctness, responsiveness, and stability. Velocity is high, fixed vs. incoming rate is about at stasis. At this point, we are looking forward to incoming Telemetry data from the Firefox 45 Beta experiment to help us evaluate readiness for 46; we should have stability and responsiveness data around Feb 18th (possibly sooner).
Why yellow? e10s is designated 'yellow' or 'at risk' because:
The team continues to work at a high velocity with 14 M8 issues open; the Telemetry A/B testing for Beta 44 didn't yield the level reliable, actionable data we were anticipating (See: http://pastebin.com/SUT7WPkq). We have since addressed the known issues and are more confident in the Beta 45 Telemetry A/B test; the project will remain yellow until we have incoming measurements and subsequent evaluation (and will likely stay yellow until we are in Firefox 46 Beta and approach our final go/no-go).
Highlights and Accomplishments
We recently landed and uplifted high value fixes to Firefox 45 in preparation for the A/B testing, this includes stability fixes and notably enabling the pref to outlaw unsafe CPOWs, See:http://pastebin.com/Qzh1cLxu.
Fixes to the BHR measurement to ensure we get good responsiveness measurements during Beta 45 A/B testing were also landed/uplifted.
As our risk of unknown unknowns begin to decrease for 46, some of us need to start to drill down into 47 as we'd like to include users with compatible Add-Ons. In order to prepare for this, we are using BHR Telemetry data to generate a whitelist/blacklist/graylist of Add-Ons based on how often they jank e10s Firefox. As Engineering continues to converge on M8, and the 45 A/B testing deployed, Product and Program will shift focus to tightening up the final plan of record for Add-Ons in an e10s world.
Program will also be engaging with more cross-functional teams as we get closer to Beta 46 (mid-Feb).
Validation for Stability and Performance
- Beta 45 A/B Telemetry Experiment was deployed on time on Jan 28. Phase 1 includes users with add-ons to detect which ones are causing jank. Phase 2 which will kick off around Feb 11th. The following fixes were landed and uplifted to improve the data collected during this round (there may be more):
- Also see:
- Upcoming Milestones:
- Feb 11: Phase 2 starts
- Feb 25: Testing concludes for 45
Look here for more milestones tracking actions around incoming data/any adjustments we need to make
Add-Ons + WebExtensions
- Devs are looking for open bugs in webextensions API
- Working to converge SDK issues: https://docs.google.com/document/d/1v0tsxR2OS0eKY2mzDvadrkl-WTjNN-wr9qKU8rpJLa4/edit
- (Carry Over)We have a meeting next week with Product to review Use cases then UX/dev priorities/realities for roll-out selection capabilities for e10s with regards to add-ons (allow/deny lists).
- (Carry Over)We need to make progress on creating a white/black/grey list for incompatible add-ons bug 1233455. The first phase of the Telemetry A/B experiment launching on the 27th will be focused on curating data to help create this black list.
- Source of truth for add-ons for priority and status on compatibility can be found, here.
Highlights and Accomplishments
- bug 1186966 - Let e10s tests ride the trains
- Browser Chrome + and Mochi Test Plan (blocks). Need to get to 90%.
- Need to make sure that M-C and M-A are in lock step
- Goal to get all tests signed-off in M/C by Feb 29th
- Here is a good test-by-test reference:
- Wiki to track work is, here.
- Currently focusing on test remoting of a11y calls from main process.
- Good progress is being made on a11y work in general; I will be tracking more closely once we're done with M8.
Current Plan of Record is to Target 100% of the population who do not have add-ons installed or a11y features enabled for Firefox 46.
|3-30||40 default (working on m5)||39 off||38 off||37 off|
|5-11||41 default (working on m6)||40 prompt||39 off||38 off|
|6-29||42 default (working on m7/m8)||41 prompt||40 off||39 off|
|8-10||43 default (working on m8)||42 default||41 off||40 off|
|9-21||44 default (release criteria driven)||43 default||42 off||41 off|
|11-02||45 default (release criteria driven)||44 default||43 off||42 off|
|12-14||46 default (release criteria driven)||45 default||44 A/B||43 off|
|1-25||47 default (release criteria driven)||46 default||45 A/B||44 off|
|3-07||48 default (release criteria driven)||47 default||46 50-50 (addons & a11y = off)||45 off|
|4-18||49 default (release criteria driven||48 default||47 50-50 (addons & a11y = off)||46 on (addons & a11y = off)|
Check back here to see interim milestones as they are created
|[DONE]||Nov 9||Aurora 43.0 Telemetry Experiment Results||Performance Team|
|[DONE]||Dec 4||Final Plan of Record Approved||Product/Engineering|
|[DONE]||Dec 14||Merge Day - 44.0 B1 GTB||RelMan|
|[DONE]||Dec 15||43.0 GA - e10s Disabled||RelMan|
|[DONE]||Dec 20||44.0 Beta 1 - e10s A/B Testing enabled||Performance Team/RelMan|
|[DONE]||Dec 28||Firefox 45 Go/No-Go||Decision Makers|
|[DONE]||Jan 3||44.0 Beta - e10s A/B Testing disabled||Performance/RelMan|
|[DONE]||Jan 27||45.0 Beta - e10s A/B Test Deployed||Performance/RelMan|
|[ON TRACK]||Feb 11||Phase 1 of A/B Test (add-ons) transitions to Phase 2 (no add-ons)||e10s team|
|[ON TRACK]||March 7||Merge Day, 46 is in Beta + M8's are at Zarro||RelEng|
|[ON TRACK]||April 19||46 GA||RelEng|