Release Management/Goals/2014Q4: Difference between revisions

Line 3: Line 3:
== Release Management General ==
== Release Management General ==
; Release Quality - Improve automation / reduce risk of manual errors
; Release Quality - Improve automation / reduce risk of manual errors
* [Lukas] Create automated release checklist (maybe based on ship-it)
* [Lukas] <stretch> Create automated release checklist (maybe based on ship-it)
* [Sylvestre] Fully automate Product-Details (if missed in Q3)
* [Sylvestre] Fully automate Product-Details
** see https://github.com/mozilla/relman-tools/tree/master/auto-pd which is a bit janky because of ftp data pulled (version is not always correct, needs more robust tests before it can be automated)
** see https://github.com/mozilla/relman-tools/tree/master/auto-pd which is a bit janky because of ftp data pulled (version is not always correct, needs more robust tests before it can be automated)


Line 14: Line 14:
* [Sylvestre] Automate the publication of Firefox Android
* [Sylvestre] Automate the publication of Firefox Android
** Use the Google play API to push APK automatically ({{bug|1045531}})
** Use the Google play API to push APK automatically ({{bug|1045531}})


; Release Quality - Find issues earlier
; Release Quality - Find issues earlier
Line 20: Line 19:
** Add in ESR
** Add in ESR
** Get Firefox Android queries/groups created
** Get Firefox Android queries/groups created
** Triage queries
** Include Triage queries
** Get external data visualized on it - stability/performance metrics so that we can get this public-facing
** Get external data visualized on it - stability/performance metrics so that we can get this public-facing
* [Lawrence] Add new repository hooks
* [Lawrence] Create checkIID hook to catch required UUID bumps
** Create checkIID hook to catch required IIDL bumps
 
; Enterprise - Improve Quality for Orgs using ESR
* [Benjamin] Investigate Automation of building MSI Installers
* [Benjamin] Move ESR Strategy Forward


; Communication
; Communication
Line 33: Line 27:
** This improves public perception of the product and also helps our enterprise sysadmins have the info they need to keep using Firefox in large deployments
** This improves public perception of the product and also helps our enterprise sysadmins have the info they need to keep using Firefox in large deployments
* [Lawrence] Find ways to improve org's understanding of current tracking and release schedule
* [Lawrence] Find ways to improve org's understanding of current tracking and release schedule
* Continue to refine team wiki
* [all] Continue to refine team wiki
 
; Release Strategy
* [Lawrence] Create release strategy document summarizing plans for improvements to measurement, process, issue mitigation, turnaround time, and automation.


; Expand contributor involvement
; Expand contributor involvement
* [?] Define contributor pathways
* [Lukas] <stretch> Define contributor pathways
** Triage of Desktop, Mobile, B2G, Platform, Services (?) bugs
** Triage of Desktop, Mobile, B2G, Platform, Services (?) bugs


* [Haseeb]
* [Haseeb] Attend CrashStats Meeting
** Start shadowing Benjamin on Nightly Triage
** Start attending CrashStats Meeting
** Start reading Agile/Release Management Book


== Firefox Desktop/Mobile ==
== Firefox Desktop/Mobile ==
* Manage and coordinate active Firefox and Firefox for Android releases
** [Lawrence] Firefox 32
** [Sylvestre] Firefox 33
** [Lawrence] Firefox 34
** [Lukas] Firefox 35
** [Sylvestre] Firefox 36
* [Lukas] <b><platform></b> Throttling improvements - finalize data gathered between FF31-33, implement updated SOP
* [Lukas] <b><platform></b> Throttling improvements - finalize data gathered between FF31-33, implement updated SOP
** Round 2 of experiments to get within the same week as release
** Round 2 of experiments to get within the same week as release
Line 55: Line 55:
** Release Notes & PR - overhaul and creating a high-signal method for generation of our release communications
** Release Notes & PR - overhaul and creating a high-signal method for generation of our release communications
** Where are we in the release cycle and what does that mean to you? (dev/qa/pr/other?)
** Where are we in the release cycle and what does that mean to you? (dev/qa/pr/other?)
* [Haseeb] Shadow Benjamin on Nightly Triage
== Firefox ESR ==
* [Benjamin] Create plan for mozilla.org changes to better expose ESR
* [Benjamin] Investigate building MSI Installers for ESR
* [Benjamin] Investigate marketing for ESR


== Special Projects ==
== Special Projects ==
Line 72: Line 78:
** Improve documentation/usability of the various tests
** Improve documentation/usability of the various tests
** Implement some features in treeherder (like the ETA) {{bug|1052397}}
** Implement some features in treeherder (like the ETA) {{bug|1052397}}
*


== Personal Development ==
== Personal Development ==
* [Bhavana]
* [Lawrence] Learn about Google Analytics
* [Lawrence] Learn about Google Analytics
* [Lukas] Back to guitar playing! Get above 80% on at least 2 songs I used to play, and get 2 new songs into the above 80% range
* [Lukas] Back to guitar playing! Get above 80% on at least 2 songs I used to play, and get 2 new songs into the above 80% range
* [Sylvestre] Continue Spanish lessons  
* [Sylvestre] Continue Spanish lessons  
* [Benjamin] Take some Banjo classes
* [Benjamin] Take some Banjo classes
* [Haseeb] Focus on communications skill
* [Haseeb] Focus on communications skill, start reading Agile/Release Management Book
Confirmed users
2,473

edits