Release Management/2014 Q1 Work Week/Desktop Mobile 2014 Focus Notes

Desktop & Mobile 2014:

• Shipping Australis, Firefox Accounts, Sync re-vamp with high quality
• Metro being a new supported product/platform - in the Windows App Store?
• Community Release Managers: generating impact reports (automated), training on Aurora uplift approvals (Ben), getting Haseeb on stability
• Marketing & PR stop using version numbers in public-facing content
• Release Readiness Dashboard (shared with B2G)
• Coupled Trains, extending the Beta cycle for more feedback and re-packaging Aurora to be a Web Developer Preview so we have a specific audience there while moving it to be in tandem with Nightly, not its own cycle
  • First half of 2014 focus on rebranding Aurora, not moving the trains yet
  • Second half, post-sprint implementation, focus on trying the collapsed trains (m-c & aurora in tandem) and extending Beta cycle
• Daily Betas - automated build & update of Beta builds with less intensive QA per-release but a focus on major issue verification and final sign offs
• Prioritizing stability and security bugs within the new sprint model for Desktop development
• Continuing to improve triage process, tools, and adding more robust automation that highlights release priorities to devs & team leads

Proposals:

• Communication to the community during the aurora period and after each beta releases (bug fixed / remaining, status of new features)
• Document some workflows / rules

RelMan Quality of Life:

• Get help with webapps, tools, dashboards, bugzilla reports from domain experts (bteam, webdev, releng)