Release Management/Goals/2013Q1

New Products & Initiatives

• [DONE] [akeybl/lsblakk] B2G: Implement the ongoing B2G Release Process (source/issue management, builds, updates, release notes, etc.)
  • https://wiki.mozilla.org/Release_Management/B2G_Landing
  • bug 837850 will add multi-select boxes to bugzilla to aid in partner/version tracking/status queries
• [DONE] [bajaj] Metro: Aid in the coordination of Metro builds (beta/release, as necessary)
  • Helped co-ordinate with Test infrastructure set-up which is completed now and we have the needed hardware set-up
  • Continued efforts to make sure we have the needed tests in place for Metro
  • QA to start adding mozmill tests soon
  • Ongoing discussion with Metro team to sync Firefox metro iteration's with our Release cycle . Tracked here
• [DONE] [KaiRo/bajaj] Stability: Coordinate the changes necessary to make longstanding stability issues actionable
  • Revisited & updated TopCrash criteria
  • Went through the crash reports and identified long standing Dektop/Android issues and prioritized them based on volume/platform (Check https://etherpad.mozilla.org/stability-centric)
  • Had a meeting involving JS & Socorro team to better understand socorro user stories and accommodate a few requests which would help JS team with crash analysis (Check https://etherpad.mozilla.org/socorro-js-userstories)
  • Bugs filed for socorro team : bug 840249,bug 838251,bug 840240,bug 803209,bug 768059
  • Next Actions : Push above bugs in the socorro priority Queue
• [DONE] [akeybl/lsblakk] Firefox: Coordinate work towards Daily Betas in RelEng/QA/A-Team
  • QA is now able to turn around a beta in 1-2 days, and RelEng has given us access to their ship-it build app to directly request builds

Documentation & Communication

• [ON TRACK] Put together new calendaring that separates meetings from events, and consider separating even more so based upon audience (for instance bug 816415)
• [DONE] [lsblakk] Document the process of bringing up a new release manager
  • Day One
  • Week/Month Overview
• [DONE] [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.
  • User:Bhavana/Day One New Hire Documentation

Automating

• [DONE] [lsblakk/akeybl] Automate the sending of frequent tracking/landing nags to bug assignees
• [ON TRACK] [lsblakk] Add nagging for 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
• [DONE] [akeybl] Work to automate merge days
  • Created merge_help.py, which removes all of the manual file changes required by https://wiki.mozilla.org/Release_Management/Merge_Documentation. Will be used for the first time on the 4/1 merge day

Elevating

• [ON TRACK] [lsblakk] Continue working with our intern towards an engineering dashboard, and make sure we don't duplicate Kyle's work
  • Sub-goal: [ON TRACK] Determine how to keep longstanding issues on the radar of engineering teams, even once they're untracked (new keywords like topcrash)
• [DONE] [akeybl]Continue look into measurements that allow us to compare releases and identify pain points (Matt's user sentiment, Kyle's tracking analysis, etc.)
  • See https://etherpad.mozilla.org/release-quality and https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnSnd5sV2HeVdEZsV05BSlRlVXkxQlF2bThOdDlDTWc&usp=sharing#gid=0

Team Focuses

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