Confirmed users
1,798
edits
(→Q2) |
(→Q2) |
||
Line 2: | Line 2: | ||
==Q2== | ==Q2== | ||
=== Forward Progress === | === Forward Progress === | ||
* Line up Rapid Betas for when FF15 is on Beta (after 7/17) | * {{ok|Line up Rapid Betas for when FF15 is on Beta (after 7/17)}} | ||
* Line up MU channel switching for when FF15 is on Beta (After 7/17) | * {{ok|Line up MU channel switching for when FF15 is on Beta (After 7/17)}} | ||
=== Coordination === | === Ongoing Coordination === | ||
* Continued coordination of FF mainline, ESR, and mobile | * {{ok|Continued coordination of FF mainline, ESR, and mobile}} | ||
* Successfully launch Fennec Native (beta and release) | * {{ok|Successfully launch Fennec Native (beta and release)}} | ||
* Complete EOL of 3.6 | * {{ok|Complete EOL of 3.6}} | ||
* Begin release management of B2G | * {{ok|Begin release management of B2G}} | ||
* Continue to prevent chemspills through regular triage | * {{ok|Continue to prevent chemspills through regular triage}} | ||
=== Process === | === Improving Process === | ||
* 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}} | ||
* 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.)}} | ||
* Improve documentation around 6-weekly processes | * {{ok|Improve documentation around 6-weekly processes}} | ||
* 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.)}} | ||
=== Data === | === Staying Data Driven === | ||
* Start to understand the difference in diversity of Beta and Release populations, and take action based upon that understanding | * {{ok|Start to understand the difference in diversity of Beta and Release populations, and take action based upon that understanding}} | ||
* Start thinking about the lifecycle of a tracked bug and measuring success of rapid releases (start analyzing our release habits and data) | * {{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|*]] | [[category:Release_Management|*]] |