Release Management/Goals: Difference between revisions

← Older edit

Release Management/Goals (view source)

Revision as of 19:07, 25 February 2016

1,116 bytes removed , 25 February 2016

m

fixed links to look nicer

Lizhenry

Confirmed users

2,816

edits

@@ Line 1: / Line 1: @@
 =2012=
-==Q2==
+[https://wiki.mozilla.org/Release_Management/Goals/2012Q2 Q2]
-=== Forward Progress ===
+[https://wiki.mozilla.org/Release_Management/Goals/2012Q4 Q4]
-* {{ok|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 ===
+=2015=
-* {{ok|Continued coordination of FF mainline, ESR, and mobile}}
+[https://wiki.mozilla.org/Release_Management/Goals/2015Q1 Q1]
-* {{ok|Successfully launch Fennec Native (beta and release)}}
-* {{ok|Complete EOL of 3.6}}
-* {{ok|Begin release management of B2G}}
-* {{ok|Continue to prevent chemspills through regular triage}}
-=== Improving Process ===
+=2016=
-* {{ok|Make improvements to bugzilla tracking/status/template and fix other process pain points}}
+[https://wiki.mozilla.org/Release_Management/Goals/2016Q1 Q1]
-* {{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|Improve channel meetings through automated creation of channel notes}}
-=== 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|*]]