MozillaWiki

Release Management/Goals/2012Q4: Difference between revisions

Page Discussion

Release Management/Goals/2012Q4 (view source)

Revision as of 19:38, 21 September 2012

40 bytes removed ,  21 September 2012
no edit summary
No edit summary
No edit summary
Line 2: Line 2:
* {{ok|[akeybl] Determine an ongoing B2G release/meeting/triage process (v1 updates and v2) [P1]}}
* {{ok|[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]}}
* {{ok|[lsblakk] Drive pre-release software quality initiative (B2G in Q4, but ongoing) [P1]}}
==== Nice to Have (2013Q1?) ====
 
* n/a
=== Documenting ===
=== Documenting ===
* {{ok|Creation of a partner "rolodex", with initial fill but also Jorge/Kev help [P1/3Days]}}
* {{ok|Creation of a partner "rolodex", with initial fill but also Jorge/Kev help [P1/3Days]}}
Line 14: Line 13:
* {{ok|[lsblakk] Revisit post-mortem and sign-off templates, ensure that actions are carried over [P2/2Days]}}
* {{ok|[lsblakk] Revisit post-mortem and sign-off templates, ensure that actions are carried over [P2/2Days]}}
* {{ok|[akeybl] Finish documentation of web content pushes & htaccess [P2/2Days]}} - https://wiki.mozilla.org/Release_Management/Release_Notes_and_Product_Details
* {{ok|[akeybl] Finish documentation of web content pushes & htaccess [P2/2Days]}} - https://wiki.mozilla.org/Release_Management/Release_Notes_and_Product_Details
==== Nice to Have (2013Q1?) ====
* New Release Manager documentation [P2/3Days]
* Add release documentation to new hire information [P3/Days]
** Outreach materials around the release process to new and existing Mozillians - slides, blogs, video
** MozCamp - keep slides available to present on a moment's notice at any  Moz-event where we might get new community release coords (or  in QA,  Sumo, Metrics, Stability, etc. who are interested in release-specific  area)
* Documenting deadlines around release notes and web content [P2/Day]


=== Automating ===
=== Automating ===
Line 27: Line 20:
* {{ok|[lsblakk] Channel meeting emails and template creation for Tuesday/Thursday [P1/2Days]}}
* {{ok|[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]}}
==== Nice to Have (2013Q1?) ====
 
* Release notes editing [P2/2Weeks]
* Web pushes (.htaccess, Release notes, product-details, and other content) [P2/2Weeks]
** Porting sqlite to MySQL db
=== Elevating ===
=== Elevating ===
* {{ok|[bajaj] Coordinate release Performance Dashboard & Alarms [P1/Ongoing]}}
* {{ok|[bajaj] Coordinate release Performance Dashboard & Alarms [P1/Ongoing]}}
* {{ok|[akeybl] Coordinate deploying of Rapid Betas [P1/Ongoing]}}
* {{ok|[akeybl] Coordinate deploying of Rapid Betas [P1/Ongoing]}}
* {{ok|[lsblakk] 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]}}
* {{ok|[lsblakk] 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]}}
==== Nice to Have (2013Q1?) ====
*  Analyze tracked bug data, fix rates, and chemspills to inform 2013 Q1  goals, looking for patterns to create best practices [P1/Days]
=== Planning for the Future (2013 Q1) ===
=== Planning for the Future (2013 Q1) ===
* {{ok|[bajaj/lsblakk] Evaluating and possibly planning a stability-centric release for longstanding stability issues [P3]}}
* {{ok|[bajaj/lsblakk] Evaluating and possibly planning a stability-centric release for longstanding stability issues [P3]}}
* {{ok|[akeybl] Spec a developer bug dashboard for an intern to pick up in 2013 [P3]}}
* {{ok|[akeybl] Spec a developer bug dashboard for an intern to pick up in 2013 [P3]}}
==== Nice to Have (2013Q1?) ====
* Plan for community release coordinators - need to understand the work  that the community can help with (unrelated to critical decision  making)  [P3]


=== Team Focuses ===
=== Team Focuses ===
Line 48: Line 33:
* Ensure that no more than 2 RMs are in the same meeting (unless staff)
* Ensure that no more than 2 RMs are in the same meeting (unless staff)
* Begin attending engineering team meetings (gfx, necko, etc.) to review tracked bug status
* Begin attending engineering team meetings (gfx, necko, etc.) to review tracked bug status
=== Nice to Haves (2013Q1?) ===
==== Documenting ====
* New Release Manager documentation [P2/3Days]
* Add release documentation to new hire information [P3/Days]
** Outreach materials around the release process to new and existing Mozillians - slides, blogs, video
** MozCamp - keep slides available to present on a moment's notice at any  Moz-event where we might get new community release coords (or  in QA,  Sumo, Metrics, Stability, etc. who are interested in release-specific  area)
* Documenting deadlines around release notes and web content [P2/Day]
==== Automating ====
* Release notes editing [P2/2Weeks]
* Web pushes (.htaccess, Release notes, product-details, and other content) [P2/2Weeks]
** Porting sqlite to MySQL db
==== Elevating ====
*  Analyze tracked bug data, fix rates, and chemspills to inform 2013 Q1  goals, looking for patterns to create best practices [P1/Days]
==== Planning for the Future ====
* Plan for community release coordinators - need to understand the work  that the community can help with (unrelated to critical decision  making)  [P3]
Akeybl
Confirmed users
1,798

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/472708"