Release Management/Goals: Difference between revisions
Jump to navigation
Jump to search
(→Q2) |
|||
| Line 13: | Line 13: | ||
=== Improving Process === | === Improving Process === | ||
* {{done|Create an intelligent team email nagger for tracked bugs}} | |||
* {{ok|Make improvements to bugzilla tracking/status/template and fix other process pain points}} | * {{ok|Make improvements to bugzilla tracking/status/template and fix other process pain points}} | ||
* {{ok|Come up with a proposal of what to do about lingering topcrash bugs (stability focus release, incentives, etc.)}} | * {{ok|Come up with a proposal of what to do about lingering topcrash bugs (stability focus release, incentives, etc.)}} | ||
* {{ok|Improve documentation around 6-weekly processes}} | * {{ok|Improve documentation around 6-weekly processes}} | ||
* {{ok|Help improve pain points for RelEng and QA (l10n, merge days, communications, etc.)}} | * {{ok|Help improve pain points for RelEng and QA (l10n, merge days, communications, etc.)}} | ||
* {{ok|Improve channel meetings through automated creation of channel notes}} | |||
=== Staying Data Driven === | === Staying Data Driven === | ||
Revision as of 22:15, 17 May 2012
2012
Q2
Forward Progress
- [ON TRACK] Line up Rapid Betas for when FF15 is on Beta (after 7/17)
- [ON TRACK] Line up MU channel switching for when FF15 is on Beta (After 7/17)
Ongoing Coordination
- [ON TRACK] Continued coordination of FF mainline, ESR, and mobile
- [ON TRACK] Successfully launch Fennec Native (beta and release)
- [ON TRACK] Complete EOL of 3.6
- [ON TRACK] Begin release management of B2G
- [ON TRACK] Continue to prevent chemspills through regular triage
Improving Process
- [DONE] Create an intelligent team email nagger for tracked bugs
- [ON TRACK] Make improvements to bugzilla tracking/status/template and fix other process pain points
- [ON TRACK] Come up with a proposal of what to do about lingering topcrash bugs (stability focus release, incentives, etc.)
- [ON TRACK] Improve documentation around 6-weekly processes
- [ON TRACK] Help improve pain points for RelEng and QA (l10n, merge days, communications, etc.)
- [ON TRACK] Improve channel meetings through automated creation of channel notes
Staying Data Driven
- [ON TRACK] Start to understand the difference in diversity of Beta and Release populations, and take action based upon that understanding
- [AT RISK] Start thinking about the lifecycle of a tracked bug and measuring success of rapid releases (start analyzing our release habits and data)