Release Management/Goals/2013Q3

General Engineering

• Become more involved in the community
  • [ON TRACK] Each RM should write at least 3 blog (or dev.planning) posts explaining/proposing RM processes and improvements
  • [ON TRACK] Prepare a Summit presentation with a similar focus to the above blog posts
• Continue our tools & automation work
  • [ON TRACK] Round 2 of the release dashboard (continued from Q2 2013)
  • [ON TRACK] Round 2 of the merge day script - single push button (continued from Q2 2013)
  • [?] [ON TRACK] Automate the update of product-details

Firefox Desktop/Mobile

• Re-focus RM efforts on mozilla-central
  • [ON TRACK] Involve integrators in the enforcement of good development practice, and possibly other tasks (such as daily changeset notes)
  • [ON TRACK] Place an "advertisement" for a Community Release Manager, focusing on Nightly noms and tracked bugs
  • [ON TRACK] Consider other new opportunities to increase quality earlier in the release, as we did with Rapid Betas

Firefox OS

• Get even more involved with the details of B2G
  • [ON TRACK] Participate in driving daily B2G smoketest blockers, ensuring a timely backout of the regressing bug
  • [ON TRACK] Ensure that at least one RM is testing each day's B2G build, filing bugs as necessary
• Get rid of new B2G partner confusion around triage
  • [ON TRACK] Enable TAMs to quickly bring a partner into the triage loop, as much through documentation as possible
  • [ON TRACK] Refine/document the process of how each partner can block a specific bug (continued from Q2 2013)
  • [ON TRACK] Create a set of rules, expectations, and separation of responsibility for triage
• Create external pre-release populations for B2G
  • [ON TRACK] Meet with GP to improve quality and frequency of builds, and coordinate feedback from their customers (OEM pre-release program)
  • [ON TRACK] Use the reference hardware for v1.2 to build to build a pre-release population (Mozilla pre-release program)