canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/Nov6: Difference between revisions
Jump to navigation
Jump to search
→Exec Status
No edit summary |
|||
| Line 6: | Line 6: | ||
==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 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. | *'''Valdiation for Stability and Performance ''' | ||
*'''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. | **'''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. Landing {{bug|1221674}} in time for Beta 4 is at risk. Meta bug tracking this = {{Bug|1222894}}. | |||
*Add- | '''*Add-Ons + WebExtensions''' | ||
** Product has requested Add-ons team aggressively outreach to devs | |||
** Helpful tool: http://arewee10syet.com/ | |||
**'''We will NOT block on slow add-on watcher''' 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. | |||
** Shell and elan are working on how to best track the plan for WebExtenstions (milestones, etc). Need to lock down Webextensions criteria in doc | |||
*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. | ||
*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. | |||