canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/May20: Difference between revisions
→Executive Summary
| Line 5: | Line 5: | ||
* The biggest news is that the e10s [https://wiki.mozilla.org/Electrolysis/Experiments#Beta_47 Experiment for Firefox 47] Beta has been approved to run for the entire Beta cycle (vs. being disabled at Beta 6). This means that stability is trending in the right direction and that RelMan has been provided the [https://sql.telemetry.mozilla.org/dashboard/release-management-dashboard Telemetry-based stability dashboard] they need to easily decipher e10s vs. non-e10s crashes. The experiment will end when Firefox 47 goes to GA on June 7 and we will repeat a similar experiment for Firefox Beta 48 with an eye towards shipping to 1% of our Firefox 48 GA population so long as we meet our Release Criteria. | * The biggest news is that the e10s [https://wiki.mozilla.org/Electrolysis/Experiments#Beta_47 Experiment for Firefox 47] Beta has been approved to run for the entire Beta cycle (vs. being disabled at Beta 6). This means that stability is trending in the right direction and that RelMan has been provided the [https://sql.telemetry.mozilla.org/dashboard/release-management-dashboard Telemetry-based stability dashboard] they need to easily decipher e10s vs. non-e10s crashes. The experiment will end when Firefox 47 goes to GA on June 7 and we will repeat a similar experiment for Firefox Beta 48 with an eye towards shipping to 1% of our Firefox 48 GA population so long as we meet our Release Criteria. | ||
* As of this week, 800,000 users have been exposed to e10s in Beta. Our two biggest risk areas remain stability and slow script count. Stability has benefited from continued focus on fixing top crashes and uplifting them. Through continued analysis, we've found landed on some interesting conclusions which lead us to be optimistic about progress, see information, here. | * As of this week, 800,000 users have been exposed to e10s in Beta. Our two biggest risk areas remain stability and slow script count. Stability has benefited from continued focus on fixing top crashes and uplifting them. Through continued analysis, we've found landed on some interesting conclusions which lead us to be optimistic about progress, see information, [https://wiki.mozilla.org/E10s/Status/May20#Release_Criteria here]. | ||
==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | ==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | ||