Release Management/Goals/2012Q2

From MozillaWiki
Jump to: navigation, search

Forward Progress

  • [AT RISK] Line up Rapid Betas for when FF15 is on Beta (after 7/17)
  • [ON TRACK] Line up MU channel switching for when FF15 is on Beta (After 7/17)

Ongoing Coordination

  • [ON TRACK] Continued coordination of FF mainline, ESR, and mobile
  • [ON TRACK] Successfully launch Fennec Native (beta and release)
  • [DONE] Complete EOL of 3.6
  • [ON TRACK] Begin release management of B2G
  • [ON TRACK] Continue to prevent chemspills through regular triage
  • [DONE] Ensure we are prepared for upcoming OS releases (Mac OS X 10.8, Windows 8)

Improving Process

  • [ON TRACK] Make improvements to bugzilla tracking/status/template and fix other process pain points
  • [ON TRACK] Come up with a proposal of what to do about lingering topcrash bugs (stability focus release, incentives, etc.)
  • [ON TRACK] Improve documentation around 6-weekly processes
  • [ON TRACK] Help improve pain points for RelEng and QA (l10n, merge days, communications, etc.)

Improving Tools

  • [DONE] Create an intelligent team email nagger for tracked bugs
  • [ON TRACK] Create "merge script" based upon merge documentation
  • [AT RISK] Improve channel meetings through automated creation of channel notes
  • [ON TRACK] Work out any remaining bugs with the release notes tool)
  • [ON TRACK] Start planning web front-end for release note tool

Staying Data Driven

  • [ON TRACK] Start to understand the difference in diversity of Beta and Release populations, and take action based upon that understanding
  • [AT RISK] Start thinking about the lifecycle of a tracked bug and measuring success of rapid releases (start analyzing our release habits and data)