Release Management/Goals/2012Q4

New Process

• [DONE] [akeybl] Determine an ongoing B2G release/meeting/triage process (v1 updates and v2) [P1]
• [DONE] [lsblakk] Drive pre-release software quality initiative (B2G in Q4, but ongoing) [P1]

Documenting

• [DONE] Creation of a partner "rolodex", with initial fill but also Jorge/Kev help [P1/3Days]
• [DONE] [akeybl] Standardize OS EOL [P1/1Day]
  • https://wiki.mozilla.org/Release_Management/OS_EOL
• [ON TRACK] [lsblakk/akeybl] Document add-on hotfix process and contacts [P1/1Day] - started docs here: https://etherpad.mozilla.org/hotfixing
• [ON TRACK] [akeybl] Document all chemspills since rapid release w/ bugs, dates, and reasoning [P1/3Days]
• [DONE] [bajaj] Document/standardize "worry list", merge documentation per merge-day [P2/2Days]
• [DONE] [lsblakk] Revisit post-mortem and sign-off templates, ensure that actions are carried over [P2/2Days]
• [DONE] [akeybl] Finish documentation of web content pushes & htaccess [P2/1Day]
  • https://wiki.mozilla.org/Release_Management/Release_Notes_and_Product_Details

Automating

• [DONE] [lsblakk] Standardize on a Release Management web server (external/internal) brainstorming [Ongoing]
  • working with Mozilla github instead of personal accounts
• [AT RISK] [akeybl] Merge Days [P1/2Weeks]
• [DONE] [lsblakk] Channel meeting emails and template creation for Tuesday/Thursday [P1/2Days]
• [ON TRACK] [bajaj] Push button nag template editing, and tracking & landing emails [P2/1Week]

Elevating

• [AT RISK] [bajaj] Coordinate release Performance Dashboard & Alarms [P1/Ongoing]
• [AT RISK] [akeybl] Coordinate deploying of Rapid Betas [P1/Ongoing]
• [DONE] [lsblakk] Twitter Account! Set up a new Release Management communication channel (Twitter/blog/etc.) to more clearly get release info out (creating a voice/culture in Mozilla) -- get key followers, module owners - market the channel & link to longer pieces as needed [P3/Ongoing]

Planning for the Future (2013 Q1)

• [ON TRACK] [bajaj/kairo] Evaluating and possibly planning a stability-centric release for longstanding stability issues [P3]
• [ON TRACK] [akeybl] Spec a developer bug dashboard for an intern to pick up in 2013 [P3]

Team Focuses

• [DONE] Complete the implementation of 1 RM per Release model
• [DONE] Ensure that no more than 2 RMs are in the same meeting (unless staff)
• [DONE] Begin attending engineering team meetings (gfx, necko, etc.) to review tracked bug status

Nice to Haves (2013Q1?)

Documenting

• New Release Manager documentation [P2/3Days]
• Add release documentation to new hire information [P3/Days]
  • Outreach materials around the release process to new and existing Mozillians - slides, blogs, video
  • MozCamp - keep slides available to present on a moment's notice at any Moz-event where we might get new community release coords (or in QA, Sumo, Metrics, Stability, etc. who are interested in release-specific area)
• Documenting deadlines around release notes and web content [P2/Day]

Automating

• Release notes editing [P2/2Weeks]
• Web pushes (.htaccess, Release notes, product-details, and other content) [P2/2Weeks]
  • Porting sqlite to MySQL db
• Tracking burndown dashboard - OPW intern Jan-April 2013 (see application for engineers individually, by team, and then for RelMan itself)

Elevating

• Analyze tracked bug data, fix rates, and chemspills to inform 2013 Q1 goals, looking for patterns to create best practices [P1/Days]

Planning for the Future

• Plan for community release coordinators - need to understand the work that the community can help with (unrelated to critical decision making) [P3]