Release Management/Goals/2014Q1: Difference between revisions
< Release Management | Goals
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
=== General Engineering === | === General Engineering === | ||
* '''Become more involved in the community''' | * '''Become more involved in the community''' | ||
** | ** 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 | *** {{miss|[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 | *** {{ok|[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|[preeti] Current issues with B2G, How is Release Management at Mozilla different from Juniper Networks}} | ||
*** | *** {{done|[sylvestre] [http://sylvestre.ledru.info/blog/2014/02/11/hello-planet-mozilla joining Mozilla]}} | ||
*** [willie] | *** [willie] | ||
*** [alco] | *** [alco] | ||
| Line 12: | Line 11: | ||
* ''' Continue our tools & automation work''' | * ''' Continue our tools & automation work''' | ||
** {{ | ** {{done||Deliver a Release Readiness Dashboard}} [bajaj, willie]}} | ||
** {{ | ** {{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 | ||
**** move off personal server to PAaS deploy | **** move off personal server to PAaS deploy | ||
**** custom view default per org chart (target audience: eng. mgr) | **** custom view default per org chart (target audience: eng. mgr) | ||
** <strike>Bug fixes and ESR support to merge-helper scripts</strike> (handed off to releng) | ** {{drop|<strike>Bug fixes and ESR support to merge-helper scripts</strike> (handed off to releng)}} | ||
** Round 2 on auto-updating product-details (we're still a quarter out from no longer needing to edit) | *** moved merge operations to releng instead | ||
** {{drop|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''' | * '''Work Week Planning for 2014''' | ||
** {{ | ** {{done|Complete separation of focus between desktop/mobile and OS}} [bajaj] | ||
=== Firefox Desktop/Mobile === | === Firefox Desktop/Mobile === | ||
Revision as of 15:33, 24 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]
- Each RM should write blog (or dev.planning) posts explaining/proposing RM processes and improvements
- Continue our tools & automation work
- [DONE] [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)
- [lsblakk] continue improvements to allow for use by wider audience (managers, devs) - public 'release' but still on staging env at first
- [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
[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]
- 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
- Work done so far: