E10s/Status/Nov27: Difference between revisions

From MozillaWiki
< E10s‎ | Status
Jump to navigation Jump to search
No edit summary
No edit summary
Line 19: Line 19:
**'''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
**'''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


*'''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 for some segment of the population 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.
   
   
*'''Automated tests:'''  
*'''Automated tests:'''  

Revision as of 18:23, 26 November 2015

Yellow-sm.jpg



10s Weekly Update: Nov 27

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. New milestone for final POR is Dec 4th. Plan of record means our schedule is finalized, we have a product brief to share, and we have a final lock on release criteria. We are also in day-for-day slip for the beta 43.0 telemetry experiment. 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.


  • Valdiation for Stability and Performance:
    • Aurora 43.0 A/B Telemetry Experiment results are posted, here. bug 1193089 Conclusions and action items based on findings are being triaged/discussed in a bi-weekly perf/e10s meeting. Perf plan is here, http://bit.ly/1XtGR4h.
    • Performance Tracker Meta bug 1198187
    • Dashboard to depict areas of strength and where we need to improve is in progress: bug 1210649. Next steps include identifying milestones for when this will be usable.
    • Beta 43.0 A/B Telemetry Experiment was scheduled for 11/20. We are currently in day-for-day slip with hopes to get this done for Dec 1. Meta bug = bug 1222894.
  • 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.
    • Helpful tool: http://arewee10syet.com/
    • We will NOT block on slow add-on watcher 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
  • A11y:
    • Wiki to track work is, 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.
  • 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 and Milestones

Status Date Milestone DRI
Day for Day Slip Nov 17 Beta 43.0 Telemetry Experiment Performance Team
RL/RV Work Week Desktop, Android, Services Dev
[DONE] March 25 Go/No-Go for all features in preparation for marketing/web string freeze Product, Dev, QE