canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/Nov27: Difference between revisions
Jump to navigation
Jump to search
→e10s Weekly Update: Nov 27
No edit summary |
|||
| Line 4: | Line 4: | ||
=e10s Weekly Update: '''Nov 27 ''' = | =e10s 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. | 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. In the | We are also in day-for-day slip for the beta 43.0 telemetry experiment. In the parallel, 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. | ||