Release Management/Goals/2015Q1: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 6: Line 6:
* [Sylvestre] Ship-it: Automatically generate partials based on current release ADI
* [Sylvestre] Ship-it: Automatically generate partials based on current release ADI
* [Sylvestre] Ship-it: Automatically generate product details
* [Sylvestre] Ship-it: Automatically generate product details
* [Lukas] Nucleus: {{bug|1119556}} add links to staging/production notes in release edit page


; Release Quality - Find issues earlier
; Release Quality - Find issues earlier
* [all] get assignees on bugs earlier in the cycle (bonus if this was in the dashboard)


; Communication
; Communication
* [Lukas] Get the nag emails running again for Desktop/Mobile/ESR bugs


; Release Strategy
; Release Strategy
* [Lukas] RelmanDash v0.2:  Get a dashboard up in Moz Spaces with info on where we're at in the release, and visibility into what issues there are with each channel
* [Lukas/Sylvestre] Enable updates faster:  starting with 35.0 and then again with 36.0 we'll enable updates on the Friday of release week and see how that goes - collect info, bring to post-mortem.  Before 37.0 we should assess if this is going well making it the new normal


; Expand contributor involvement
; Expand contributor involvement
* [Lukas] put out the call for, interview, and onboard at least one new contributor


== Firefox Desktop/Mobile ==
== Firefox Desktop/Mobile ==

Revision as of 23:20, 8 January 2015

Release Management Q1 2015 Goals

<platform> denotes goals that are listed on the platform Q4 goals list

Release Management General

Release Quality - Improve automation / reduce risk of manual errors
  • [Sylvestre] Add capability to release notes backend (nucleus) to upload an image/video. bug 1117783, bug 1117786 and bug 1117790
  • [Sylvestre] Ship-it: Automatically generate partials based on current release ADI
  • [Sylvestre] Ship-it: Automatically generate product details
  • [Lukas] Nucleus: bug 1119556 add links to staging/production notes in release edit page
Release Quality - Find issues earlier
  • [all] get assignees on bugs earlier in the cycle (bonus if this was in the dashboard)


Communication
  • [Lukas] Get the nag emails running again for Desktop/Mobile/ESR bugs
Release Strategy
  • [Lukas] RelmanDash v0.2: Get a dashboard up in Moz Spaces with info on where we're at in the release, and visibility into what issues there are with each channel
  • [Lukas/Sylvestre] Enable updates faster: starting with 35.0 and then again with 36.0 we'll enable updates on the Friday of release week and see how that goes - collect info, bring to post-mortem. Before 37.0 we should assess if this is going well making it the new normal
Expand contributor involvement
  • [Lukas] put out the call for, interview, and onboard at least one new contributor

Firefox Desktop/Mobile

  • Manage and coordinate active Firefox and Firefox for Android releases
    • [Lawrence] Firefox 34
    • [Lukas] Firefox 35
    • [Sylvestre] Firefox 36
    • [Lawrence] Firefox 37
    • [Lukas] Firefox 38
    • [Sylvestre] Firefox 39

Firefox ESR

Special Projects

Personal Development

  • [Lawrence]
  • [Lukas]
  • [Sylvestre]
  • [Benjamin]
  • [Haseeb]