canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/Nov6: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "thumbnail|left<br> =10s Weekly Update: '''Nov 6'''= Why yellow? e10s is designated 'yellow' or 'at risk' because we need to continue to finalize the B...") |
No edit summary |
||
| Line 1: | Line 1: | ||
[[File:Yellow-sm.jpg|thumbnail|left]]<br> | [[File:Yellow-sm.jpg|thumbnail|left]]<br> | ||
=10s Weekly Update: '''Nov | =10s Weekly Update: '''Nov 13'''= | ||
Why yellow? e10s is designated 'yellow' or 'at risk' because we need to continue to finalize the Beta and GA Criteria and roll the plan into an official Plan of Record. Engineering team continues to work at high velocity and are in the midst of their final, functional milestone, M8. Validating that all of this work translates into a product we are proud of is key to our success before we do a go to market launch. | Why yellow? e10s is designated 'yellow' or 'at risk' because we need to continue to finalize the Beta and GA Criteria and roll the plan into an official Plan of Record. Engineering team continues to work at high velocity and are in the midst of their final, functional milestone, M8. Validating that all of this work translates into a product we are proud of is key to our success before we do a go to market launch. | ||
==Exec Status== | ==Exec Status== | ||
*Engineering continues to burn down M8 Issues. The M8 milestone represents the completion of all functional work deemed necessary for rollout to BETA. Remaining milestone(s) will concentrate on performance work and any incoming issues. | *'''Engineering continues to burn down M8 Issues.''' The M8 milestone represents the completion of all functional work deemed necessary for rollout to BETA. Remaining milestone(s) will concentrate on performance work and any incoming issues. | ||
*Aurora 43.0 Telemetry Experiment | *'''Aurora 43.0 A/B Telemetry Experiment''' results are posted, [http://nbviewer.ipython.org/github/vitillo/e10s_analyses/blob/master/aurora/e10s_experiment.ipynb here]. {{bug|1193089}} Conclusions and action items based on findings being discussed in a bi-weekly perf/e10s meet and resulting action items will be documented. | ||
*'''Beta 43.0 A/B Telemetry Experiment''' will kick off for Beta 4 which ships on 11/18. We are ready to go with the exception of {{bug|1198196}} which is on track to land/get uplifted by GTB for B4 on 11/16. | |||
More details can be found here {{Bug|1222894}}. | |||
*Add-on compatibility continues to be a primary focus with details available, here. Criteria for Add-Ons has been set. We need to decide what the UX will be for both general add-ons use cases and for slow add-on warnings, specifically. | *Add-on compatibility continues to be a primary focus with details available, here. Criteria for Add-Ons has been set. We need to decide what the UX will be for both general add-ons use cases and for slow add-on warnings, specifically. | ||
https://bugzilla.mozilla.org/show_bug.cgi?id=1182638#c17 | |||
*Automated tests: we are working with module owners to be sure their automated tests are groomed for e10s. We will be developing more milestones to track progress, soon. | *Automated tests: we are working with module owners to be sure their automated tests are groomed for e10s. We will be developing more milestones to track progress, soon. | ||
*Accessibility: open question whether we block on accessibility compatibility. Support is preferred for simplicity but blocking on the development will impact the schedule by up to three months. | *Accessibility: open question whether we block on accessibility compatibility. Support is preferred for simplicity but blocking on the development will impact the schedule by up to three months. | ||
*We are working on action items unearthed by our release critieria to clear the path to a final plan of record by Nov 13th. | *We are working on action items unearthed by our release critieria to clear the path to a final plan of record by Nov 13th. | ||