Release Management/Goals/2012Q4: Difference between revisions

no edit summary
No edit summary
Line 1: Line 1:
=== New Process ===
=== New Process ===
* {{ok|[akeybl] Determine an ongoing B2G release/meeting/triage process (v1 updates and v2) [P1]}}
* {{done|[akeybl] Determine an ongoing B2G release/meeting/triage process (v1 updates and v2) [P1]}}
* {{ok|[lsblakk] Drive pre-release software quality initiative (B2G in Q4, but ongoing) [P1]}}
* {{done|[lsblakk] Drive pre-release software quality initiative (B2G in Q4, but ongoing) [P1]}}


=== Documenting ===
=== Documenting ===
* {{ok|Creation of a partner "rolodex", with initial fill but also Jorge/Kev help [P1/3Days]}}
* {{done|Creation of a partner "rolodex", with initial fill but also Jorge/Kev help [P1/3Days]}}
** [akeybl/lsblakk] coming up with problematic company names, and emails we already have
** [bajaj] rolodex location/format, working with Jorge/Kev to fill in gaps
* {{done|[akeybl] Standardize OS EOL [P1/1Day]}}
* {{done|[akeybl] Standardize OS EOL [P1/1Day]}}
** https://wiki.mozilla.org/Release_Management/OS_EOL
** https://wiki.mozilla.org/Release_Management/OS_EOL
* {{ok|[lsblakk/akeybl] Document add-on hotfix process and contacts [P1/1Day]}} - started docs here: https://etherpad.mozilla.org/hotfixing
* {{ok|[lsblakk/akeybl] Document add-on hotfix process and contacts [P1/1Day]}} - started docs here: https://etherpad.mozilla.org/hotfixing
* {{ok|[akeybl] Document all chemspills since rapid release w/ bugs, dates, and reasoning [P1/3Days]}}
* {{ok|[akeybl] Document all chemspills since rapid release w/ bugs, dates, and reasoning [P1/3Days]}}
* {{ok|[bajaj] Document/standardize "worry list", merge documentation per merge-day [P2/2Days]}}
* {{done|[bajaj] Document/standardize "worry list", merge documentation per merge-day [P2/2Days]}}
* {{ok|[lsblakk] Revisit post-mortem and sign-off templates, ensure that actions are carried over [P2/2Days]}}
* {{done|[lsblakk] Revisit post-mortem and sign-off templates, ensure that actions are carried over [P2/2Days]}}
* {{done|[akeybl] Finish documentation of web content pushes & htaccess [P2/1Day]}}
* {{done|[akeybl] Finish documentation of web content pushes & htaccess [P2/1Day]}}
** https://wiki.mozilla.org/Release_Management/Release_Notes_and_Product_Details
** https://wiki.mozilla.org/Release_Management/Release_Notes_and_Product_Details


=== Automating ===
=== Automating ===
* {{ok|[lsblakk] Standardize on a Release Management web server (external/internal) [https://etherpad.mozilla.org/relman-server brainstorming] [Ongoing]}}
* {done|[lsblakk] Standardize on a Release Management web server (external/internal) [https://etherpad.mozilla.org/relman-server brainstorming] [Ongoing]}}
** working with Mozilla github instead of personal accounts
** working with Mozilla github instead of personal accounts
* {{ok|[akeybl] Merge Days [P1/2Weeks]}}
* {{risk|[akeybl] Merge Days [P1/2Weeks]}}
* {{done|[lsblakk] Channel meeting emails and template creation for Tuesday/Thursday [P1/2Days]}}
* {{done|[lsblakk] Channel meeting emails and template creation for Tuesday/Thursday [P1/2Days]}}
* {{ok|[bajaj] Push button nag template editing, and tracking & landing emails [P2/1Week]}}
* {{ok|[bajaj] Push button nag template editing, and tracking & landing emails [P2/1Week]}}


=== Elevating ===
=== Elevating ===
* {{ok|[bajaj] Coordinate release Performance Dashboard & Alarms [P1/Ongoing]}}
* {{risk|[bajaj] Coordinate release Performance Dashboard & Alarms [P1/Ongoing]}}
* {{ok|[akeybl] Coordinate deploying of Rapid Betas [P1/Ongoing]}}
* {{risk|[akeybl] Coordinate deploying of Rapid Betas [P1/Ongoing]}}
* {{done|[lsblakk] [https://twitter.com/MozillaReleases Twitter Account!] Set up a new Release Management communication channel (Twitter/blog/etc.) to more clearly get release info out (creating a voice/culture in Mozilla) -- get key followers, module owners - market the channel & link to longer pieces as needed [P3/Ongoing]}}
* {{done|[lsblakk] [https://twitter.com/MozillaReleases Twitter Account!] Set up a new Release Management communication channel (Twitter/blog/etc.) to more clearly get release info out (creating a voice/culture in Mozilla) -- get key followers, module owners - market the channel & link to longer pieces as needed [P3/Ongoing]}}


Line 33: Line 31:


=== Team Focuses ===
=== Team Focuses ===
* {{ok|Complete the implementation of 1 RM per Release model}}
* {{done|Complete the implementation of 1 RM per Release model}}
* {{ok|Ensure that no more than 2 RMs are in the same meeting (unless staff)}}
* {{done|Ensure that no more than 2 RMs are in the same meeting (unless staff)}}
* {{ok|Begin attending engineering team meetings (gfx, necko, etc.) to review tracked bug status}}
* {{done|Begin attending engineering team meetings (gfx, necko, etc.) to review tracked bug status}}


=== Nice to Haves (2013Q1?) ===
=== Nice to Haves (2013Q1?) ===
Confirmed users
1,798

edits