Release Management/Goals/2014Q1: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 11: Line 11:


* ''' Continue our tools & automation work'''
* ''' Continue our tools & automation work'''
** {{done||Deliver a Release Readiness Dashboard}} [bajaj, willie]}}
** {{done|Deliver a Release Readiness Dashboard}} [bajaj, willie]
** {{miss|Round 3 of the triage dashboard}}
** {{miss|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
*** [lsblakk] continue improvements to allow for use by wider audience (managers, devs) - public 'release' but still on staging env at first
Line 31: Line 31:


=== Firefox OS ===
=== Firefox OS ===
* <strike> {{ok |Ensure 1.4 is on-track to be delivered with high quality}} [bajaj] </strike>
* {{drop |<strike> Ensure 1.4 is on-track to be delivered with high quality  [bajaj] </strike>}}
** Preeti picked up 1.4
* {{ok |Run dogfooding program once the reference device is delivered}}  [Preeti]
* {{ok |Run dogfooding program once the reference device is delivered}}  [Preeti]
** Work done so far:
** Work done so far:

Latest revision as of 16:06, 26 March 2014

General Engineering

  • Become more involved in the community
    • Each RM should write blog (or dev.planning) posts explaining/proposing RM processes and improvements
      • [MISSED] [bajaj] Experience on working with Community Release Managers and bringing them upto speed, Metro Release
      • [ON TRACK] [lsblakk] Revised Coupled Train Model, Update on comm release managers wrt tracking volume and effectiveness, Work Week blog posts
      • [DONE] [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
    • [DONE] Deliver a Release Readiness Dashboard [bajaj, willie]
    • [MISSED] 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)
    • [DROPPED] Bug fixes and ESR support to merge-helper scripts (handed off to releng)
      • moved merge operations to releng instead
    • [DROPPED] Round 2 on auto-updating product-details (we're still a quarter out from no longer needing to edit)
      • low priority


  • Work Week Planning for 2014
    • [DONE] 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]
  • [MISSED] Work with Devs, PM team, Marketing/PR, and others to draft a proposal for a revamped Aurora -- this will go to a later quarter, after coupled train [sylvestre, lsblakk]
  • [ON TRACK] Help deliver Metro Release, current target is Firefox 28, hand off into trains [bajaj]

Firefox OS

  • [DROPPED] Ensure 1.4 is on-track to be delivered with high quality [bajaj]
    • Preeti picked up 1.4
  • [ON TRACK] Run dogfooding program once the reference device is delivered [Preeti]
    • Work done so far:
      • Initial investigation on the device itself
      • Understand update policy and what was needed for Phase 1
      • CURRENT STATUS: Awaiting reference phone
Retrieved from "https://wiki.allizom.org/index.php?title=Release_Management/Goals/2014Q1&oldid=957481"