E10s/Status/Dec17: Difference between revisions

no edit summary
No edit summary
 
(9 intermediate revisions by 2 users not shown)
Line 22: Line 22:




*'''Validation for Stability and Performance: '''
==Validation for Stability and Performance==
** Birunthan :poiru is going to post a summary of e10s vs non-e10s telemetry from the Aurora 43 experiment on the m.d.platform newsgroup this week. Draft here: https://docs.google.com/a/mozilla.com/document/d/1bRWybYcuTefO9qUPkul_r6rN-rl3QOAG_GpeJiYWhzs/edit?usp=sharing
** Birunthan :poiru is going to post a summary of e10s vs non-e10s telemetry from the Aurora 43 experiment on the m.d.platform newsgroup this week. Draft here: https://docs.google.com/a/mozilla.com/document/d/1bRWybYcuTefO9qUPkul_r6rN-rl3QOAG_GpeJiYWhzs/edit?usp=sharing
** '''Beta 44 A/B Telemetry Experiment''' is live: https://bsmedberg.github.io/telemetry-experiments-dashboard/
** '''Beta 44 A/B Telemetry Experiment''' is live: https://bsmedberg.github.io/telemetry-experiments-dashboard/
Line 28: Line 28:
*** This experiment is going to be run until January 11th (tentative end date)
*** This experiment is going to be run until January 11th (tentative end date)
** Dec 12th e10s Telemetry probe triage: [https://docs.google.com/spreadsheets/d/1FIaGNv1q750mo9S7cJJY_8erbiF7j9snyX8Yd0diAbA/edit#gid=307269420 spreadsheet]
** Dec 12th e10s Telemetry probe triage: [https://docs.google.com/spreadsheets/d/1FIaGNv1q750mo9S7cJJY_8erbiF7j9snyX8Yd0diAbA/edit#gid=307269420 spreadsheet]
** {{bug|1182637}}: the BHR/event-loop-lag responsiveness deficit in e10s has been confirmed first-hand with an extension that visualizes the BHR jank measurements: https://github.com/chutten/statuser
** {{bug|1182637}}: the BHR/event-loop-lag responsiveness regression in e10s has been confirmed first-hand with an extension that visualizes the BHR jank measurements: https://github.com/chutten/statuser
*** BHR reporting still needs to be improved to narrow down the origins: {{bug|1224374}}
*** BHR reporting still needs to be improved to narrow down the origins: {{bug|1224374}}
** There also appears to be a stability regression https://bugzilla.mozilla.org/show_bug.cgi?id=1229104#c19
** There is also a known regression in e10s page-load speed in Talos & Telemetry data
** There is also a known regression in e10s page-load speed in Talos & Telemetry data
** Telemetry E10S Measurement Meta {{Bug|1222849}}
** Performance Tracker Meta {{Bug|1198187}}
** Performance Tracker Meta {{Bug|1198187}}


*'''Add-Ons + WebExtensions:'''
==Add-Ons + WebExtensions==
** Product has requested Add-ons team aggressively outreach to devs, next steps include working with them to create some milestones around this.  
*Add-Ons 'Office Hours' to help developers with real-time support is ongoing: http://atsay.github.io/e10s_office_hours/
*We need to make progress on creating a black list for incompatible add-ons {{bug|1233455}}. Next steps include working with add-ons team to identify a DRI + connecting them telemetry data to get started.
** Source truth for add-ons for priority and status on compatibility can be found, [https://docs.google.com/spreadsheets/d/1KoJoMD4DMZ2zODnxFtzhrPHVpAH3GxTIr0fKN65dlCE/edit#gid=0 here].
** Source truth for add-ons for priority and status on compatibility can be found, [https://docs.google.com/spreadsheets/d/1KoJoMD4DMZ2zODnxFtzhrPHVpAH3GxTIr0fKN65dlCE/edit#gid=0 here].
**'''We will NOT block on slow add-on watcher''' for any GA plans.
**'''We will NOT block on slow add-on watcher''' for any GA plans.
**'''We will NOT block on WebExtensions'' for any GA plans  
**'''We will NOT block on WebExtensions'' for any GA plans  
**'''We DO need to figure out what the product requirements are''', if any for UX relating to Add-ons in an e10s world in general. This also coincides with the Shield project. UX, and Perf are engaged and we're starting conversations about user interaction and API readiness.   
**'''We DO need to figure out what the product requirements are''', if any for UX relating to Add-ons in an e10s world in general. This also coincides with the Shield project. UX, and Perf are engaged and we're starting conversations about user interaction and API readiness.   
==Automated tests==
*We're primarily missing 3 suites on Windows: mochitest-plain, reftest, and crashtest. Work needs to be done to green up each of these suites, so capacity issues are not currently the blocker.
* A-Team is currently working on disabling enough tests on mochitest-plain to get them enabled, but there is a shutdown leak on debug which is difficult to trace to a particular test. We may get those running by the end of the year, leaving only crashtests and reftests.
*Felipe is jumping in to help Blake, jgriffin, and Jim green up tests:
https://public.etherpad-mozilla.org/p/e10stests-taskforce


*'''A11y:'''
==A11y==
** Wiki to track work is, [https://wiki.mozilla.org/Accessibility/Electrolysis2 here].  
** Wiki to track work is, [https://wiki.mozilla.org/Accessibility/Electrolysis2 here].  
** '''Decision made to not block going to GA''' on A11y. We are ramping up to help be sure we do everything we can to get a good level of parity.
** '''Decision made to not block going to GA''' on A11y. We are ramping up to help be sure we do everything we can to get a good level of parity.
** We are planning on getting e10s team + Firefox functional teams together in Orlando to continue the envangelize pruning and greening up of tests on part of module owners.  
** We are planning on getting e10s team + Firefox functional teams together in Orlando to continue the envangelize pruning and greening up of tests on part of module owners.  
*'''Automated tests:'''
** We should be good to have our tests for windows enabled by Fx45/Fx46. mochitest-devtools on Windows 7 is about to be enabled {{bug|1221499}}. Server capacity is an issue we need to balance.
** All Linux tests are enabled (that are of priority).
==Release Schedule==
==Release Schedule==
Currently Proposed Schedule is to enable e10s by default for Users without Add-Ons for 45.0 and target a larger population for 46.0
Currently Proposed Schedule is to enable e10s by default for Users without Add-Ons for 45.0 and target a larger population for 46.0. As mentioned above, we'll do a go/no-go on the 28th of Dec.
 




Line 83: Line 86:
! Status !! Date !! Milestone !! DRI  
! Status !! Date !! Milestone !! DRI  
|-
|-
| {{done|}} || '''Nov 9''' || Aurora 43.0 Telemetry Experiment Results|| Performance Team
| {{done|}} || '''Nov 9''' || '''Aurora 43.0 Telemetry Experiment Results'''|| Performance Team
|-
|-
| {{mrisk}}  || '''Nov 17'''  || Beta 43.0 Telemetry Experiment Launches || Performance Team
| {{mrisk}}  || '''Nov 17'''  || '''Beta 43.0 Telemetry Experiment Launches''' || Performance Team
|-
|-
| {{mrisk}}  || '''Nov 30 || GTB Beta 7 Telemetry Experiment Final Uplifts/Testing|| Performance Team/RelMan
| {{mrisk}}  || '''Nov 30 || '''GTB Beta 7 Telemetry Experiment Final Uplifts/Testing'''|| Performance Team/RelMan
|-
|-
| {{mok}} || '''Dec 4''' || Final Plan of Record Approved|| Product/Engineering
| {{mok}} || '''Dec 4''' || '''Final Plan of Record Approved'''|| Product/Engineering
|-
|-
| {{mok}} || '''Dec 14'''|| Merge Day - 44.0 B1 GTB || RelMan
| {{mok}} || '''Dec 14'''|| '''Merge Day - 44.0 B1 GTB''' || RelMan
|-  
|-  
| {{mok}} || '''Dec 15''' || '''43.0 GA - e10s Disabled''' || 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
|-
| {{mok}} || '''Dec 28'''|| '''Firefox 45 Go/No-Go''' || Decision Makers
|-
|-
| '''TBD''' || '''Dec 16  '''|| '''44.0 Beta 1 - e10s experiment enabled(?)'''|| Performance Team/RelMan
| {{mok}} || '''Jan 11''' || '''44.0 Beta - e10s A/B Testing disabled'''|| Performance/RelMan
|-
|-
|
|}
|}
canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401

edits