|
|
| Line 1: |
Line 1: |
| =2012= | | =2012= |
| ==Q2==
| | [/2012Q2] |
| === Forward Progress ===
| | [/2012Q4] |
| * {{risk|Line up Rapid Betas for when FF15 is on Beta (after 7/17)}}
| |
| * {{ok|Line up MU channel switching for when FF15 is on Beta (After 7/17)}}
| |
| | |
| === Ongoing Coordination ===
| |
| * {{ok|Continued coordination of FF mainline, ESR, and mobile}}
| |
| * {{ok|Successfully launch Fennec Native (beta and release)}}
| |
| * {{done|Complete EOL of 3.6}}
| |
| * {{ok|Begin release management of B2G}}
| |
| * {{ok|Continue to prevent chemspills through regular triage}}
| |
| * {{done|Ensure we are prepared for upcoming OS releases (Mac OS X 10.8, Windows 8)}}
| |
| | |
| === Improving Process ===
| |
| * {{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|Improve documentation around 6-weekly processes}}
| |
| * {{ok|Help improve pain points for RelEng and QA (l10n, merge days, communications, etc.)}}
| |
| | |
| === Improving Tools ===
| |
| * {{done|Create an intelligent team email nagger for tracked bugs}}
| |
| * {{ok|Create "merge script" based upon merge documentation}}
| |
| * {{risk|Improve channel meetings through automated creation of channel notes}}
| |
| * {{ok|Work out any remaining bugs with the release notes tool)}}
| |
| * {{ok|Start planning web front-end for release note tool}}
| |
| | |
| === Staying Data Driven ===
| |
| * {{ok|Start to understand the difference in diversity of Beta and Release populations, and take action based upon that understanding}}
| |
| * {{risk|Start thinking about the lifecycle of a tracked bug and measuring success of rapid releases (start analyzing our release habits and data)}}
| |
| | |
| [[category:Release_Management|*]]
| |