E10s/Status/March25: Difference between revisions

Jump to navigation Jump to search

E10s/Status/March25 (view source)

Revision as of 21:47, 25 March 2016

3,288 bytes removed ,  25 March 2016
no edit summary
No edit summary
Line 13: Line 13:


==Highlights and Accomplishments==
==Highlights and Accomplishments==
We recently landed [https://wiki.mozilla.org/E10s/Status/m8#Landed_in_47_but_not_uplifted_to_46 the following M8's in Fx47]. Work is complete to deploy the second phase of the Telemetry A/B Experiments testing. We have some great analysis on incoming stability data from the Beta 45 experiment so far {{bug|1246180}}. Check out a summary of the engineering happenings this last week, [https://wiki.mozilla.org/Electrolysis/Meetings/2016-02-11 here].
*Check out a summary of the engineering happenings this last week,  
 
With the help of the quality team/SV, we have been conducting a backlog scrub of all the [https://bugzilla.mozilla.org/buglist.cgi?priority=--&v4=needinfo&keywords=meta%2C%20qawanted&keywords_type=nowords&f1=cf_tracking_e10s&o3=nowordssubstr&v3=1013364%2C%20984139%2C%20905436%2C%201063169%2C%20993639%2C%201004745%2C%201029143%2C%20875871%2C%20915546%2C%201207306%2C%201058354&o1=equals&resolution=---&o2=nowordssubstr&f4=flagtypes.name&query_format=advanced&f3=blocked&f2=short_desc&o4=notsubstring&v1=%2B&v2=intermittent%2C%20test%2C%20addon%2C%20add-on&list_id=12851479] issues being tracked for e10s. We've made quick progress to be sure there are not blockers or a combination small things that we would consider a negative trend and block to be found. We also wanted to be sure that we could close as many open items as possible. [https://docs.google.com/spreadsheets/d/1fEqqT05Gi3dAKbwsotmpXPO9nR19Ra4ecmCPoHqyAMg/edit#gid=995994685] See the report from SV for details.


==Next Steps==
==Next Steps==
As we continue to converge towards an eye for Firefox 46 beta, we'll need to start closely tracking M9's. As previously mentioned, focusing on our add-ons population and also being sure that we validate our measurements with real world proof is important. More details on how that will happen will be available soon. Solidifying that we have consensus and confidence in our roll-out plan is also an important next step and will be a major topic in the cross-functional kicking off next week.
*


==Validation for Stability and Performance==
==Release Criteria
*Phase 2 of the Beta 45 experiment is ready for deployment, see details, here http://pastebin.com/cNKAnW2d.
* We have solid data on stability and are taking action, see more [https://wiki.mozilla.org/Electrolysis/Meetings/2016-02-11#poiru_.28e10s_stability.29] here.
* Jank results are positive thus far though we need to be sure to validate in the real world. See prelim details, [https://wiki.mozilla.org/Electrolysis/Meetings/2016-02-11#chutten_.28e10s_responsiveness.29] here.
* Information about add-ons which are causing jank is also incoming and we need to continue to ensure it's being validated. More on this, soon.


*Upcoming Milestones:
**'''Feb 12''': 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''


== Memory Usage==
== Memory Usage==
Line 37: Line 27:
*Devs are looking for open bugs in webextensions API
*Devs are looking for open bugs in webextensions API
* Working to converge SDK issues: https://docs.google.com/document/d/1v0tsxR2OS0eKY2mzDvadrkl-WTjNN-wr9qKU8rpJLa4/edit
* 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.


==Automated tests==
==Automated tests==
* Module owners need to be sure their tests are e10s compliant.
* Goal to have all tests be owned by 03/25 is close
*Browser Chrome + and Mochi Test Plan (blocks). Need to get to 90%.
* We would like sign-off
*Need to make sure that M-C and M-A are in lock step
*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
*Goal to get all tests signed-off in M/C by Feb 29th
Line 54: Line 42:
*Currently focusing on test remoting of a11y calls from main process.
*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.
*Good progress is being made on a11y work in general; I will be tracking more closely once we're done with M8.
==Milestones==
We are at the point where we are setting milestones weekly; given the complexity of deliverables, we are using a [https://docs.google.com/spreadsheets/d/101ra3HjqyufjP79JkGa4e0RyHPLVlJXS43rXtKuoJw4/edit#gid=0%20 Trackback Schedule] to keep everything organized.


==Release Schedule==
==Release Schedule==
Line 82: Line 73:
| 4-18 || 49 default (release criteria driven || 48 default || 47 (addons & a11y = off) || 46 off
| 4-18 || 49 default (release criteria driven || 48 default || 47 (addons & a11y = off) || 46 off
|}
|}
==Milestones==
We are at the point where we are setting milestones weekly; given the complexity of deliverables, we are using a [https://docs.google.com/spreadsheets/d/101ra3HjqyufjP79JkGa4e0RyHPLVlJXS43rXtKuoJw4/edit#gid=0%20 Trackback Schedule] to keep everything organized.
ErinL ancaster
canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1124252"

Navigation menu