canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/Jan29: Difference between revisions
Jump to navigation
Jump to search
→e10s Weekly Update: Jan 29
| Line 3: | Line 3: | ||
=e10s Weekly Update: '''Jan 29'''= | =e10s Weekly Update: '''Jan 29'''= | ||
==Executive Summary== | ==Executive Summary== | ||
* The Plan of record is to enable e10s as of Firefox 46 (GA April 19). This initial GA release will be a cohort release | * 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 [https://wiki.mozilla.org/E10s/Status/m8#m8_Tracker 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. | * The team is currently focused on burning down [https://wiki.mozilla.org/E10s/Status/m8#m8_Tracker 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: == | ==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | ||
| Line 16: | Line 16: | ||
==Next Steps== | ==Next Steps== | ||
As our risk of unknown unknowns begin to decrease, we | 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== | ==Validation for Stability and Performance== | ||
| Line 32: | Line 32: | ||
**'''Feb 1''': Sanity check incoming data | **'''Feb 1''': Sanity check incoming data | ||
**'''Feb 5''': Run existing data set | **'''Feb 5''': Run existing data set | ||
'' | **'''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== | ==Add-Ons + WebExtensions== | ||
*Devs are looking for open bugs in 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 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. | *(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. | ||
| Line 41: | Line 43: | ||
==Automated tests== | ==Automated tests== | ||
* | *We'd like to do a final audit of tests on M-C by Feb 28th | ||
*Here is a good test-by-test reference: | *Here is a good test-by-test reference: | ||
https://docs.google.com/spreadsheets/d/10UeyRoiWV2HjkWwAU51HXyXAV7YLi4BjDm55mr5Xv6c/edit#gid=1777180571 | https://docs.google.com/spreadsheets/d/10UeyRoiWV2HjkWwAU51HXyXAV7YLi4BjDm55mr5Xv6c/edit#gid=1777180571 | ||