Release Management/Goals/2013Q1

New Products & Initiatives

• [ON TRACK] [akeybl/lsblakk] B2G: Implement the ongoing B2G Release Process (source/issue management, builds, updates, release notes, etc.
• [ON TRACK] [bajaj] Metro: Aid in the coordination of Metro builds (beta/release, as necessary)
• [ON TRACK] [KaiRo/bajaj] Stability: Coordinate the changes necessary to make longstanding stability issues actionable
• [ON TRACK] [akeybl/lsblakk] Firefox: Coordinate work towards Daily Betas in RelEng/QA/A-Team

Documentation & Communication

• [ON TRACK] Put together new calendaring that separates meetings from events, and consider separating even more so based upon audience
• [ON TRACK] [lsblakk] Document the process of bringing up a new release manager
• [ON TRACK] [akeybl] Come up with the process and tooling necessary to prevent release note mishaps (BZ, etc.)
• [ON TRACK] [bajaj] Identify and combat any egr. misunderstandings around timelines, tracked bugs, landing, etc.

Automating

• [ON TRACK] [lsblakk/akeybl] Automate the sending of frequent tracking/landing nags to bug assignees
• [ON TRACK] Start nagging those bugs with needinfo? that are important for a release (day-to-day)
• [ON TRACK] Automate the export of channel meeting notes from etherpad to the wiki, and the clearing of the etherpad
• [ON TRACK] [akeybl] Work to automate merge days

Elevating

• [ON TRACK] [lsblakk] Continue working with our intern towards an engineering dashboard, and make sure we don't duplicate Kyle's work
• [ON TRACK] Continue look into measurements that allow us to compare releases and identify pain points (Matt's user sentiment, Kyle's tracking analysis, etc.)
• [ON TRACK] Determine how to keep longstanding issues on the radar of engineering teams, even once they're untracked (new keywords like topcrash)

Team Focuses

• [ON TRACK] Use Asana for tracking non-bug work and coordination