Release Management/Goals/2014Q1

General Engineering

• Become more involved in the community
  • [ON TRACK] Each RM should write blog (or dev.planning) posts explaining/proposing RM processes and improvements
    • [bajaj] Experience on working with Community Release Managers and bringing them upto speed, Metro Release
    • [lsblakk] Revised Coupled Train Model, Update on comm release managers wrt tracking volume and effectiveness, Work Week blog posts
    • [preeti] Current issues with B2G, How is Release Management at Mozilla different from Juniper Networks
      • DONE
    • [sylvestre] joining Mozilla
    • [willie]
    • [alco]
    • [bkerensa]

• Continue our tools & automation work
  • [ON TRACK] Deliver a Release Readiness Dashboard [bajaj, willie]
  • [ON TRACK] Round 3 of the triage dashboard
    • [lsblakk] continue improvements to allow for use by wider audience (managers, devs) - public 'release' but still on staging env at first
      • move off personal server to PAaS deploy
      • custom view default per org chart (target audience: eng. mgr)
  • Bug fixes and ESR support to merge-helper scripts
  • Round 2 on auto-updating product-details (we're still a quarter out from no longer needing to edit)

• Work Week Planning for 2014
  • [ON TRACK] Complete separation of focus between desktop/mobile and OS [bajaj]

Firefox Desktop/Mobile

• [ON TRACK] Continue working on implementing a Coupled Train Model, blog post and discussion about the new plan (with no affect to l10n this time) goal is to finalize a plan of action to start in Q2 [lsblakk]
• [ON TRACK] Work with Devs, PM team, Marketing/PR, and others to draft a proposal for a revamped Aurora [sylvestre, lsblakk]
• [ON TRACK] Help deliver Metro Release, current target is Firefox 28, hand off into trains [bajaj]

Firefox OS

• [ON TRACK] Ensure 1.4 is on-track to be delivered with high quality [bajaj]
• [ON TRACK] Run dogfooding program once the reference device is delivered [Preeti]