Release Management/Goals/2013Q3: Difference between revisions

* '''Re-focus RM efforts on mozilla-central'''

** {{ok|Involve integrators in the enforcement of good development practice, and possibly other tasks (such as daily changeset notes)}}

** {{ok|Place an "advertisement" for a Community Release Manager focusing on Nightly noms and tracked bugs, and begin interviews}}

=== Firefox OS ===

* '''Get even more involved with the details of B2G'''

** {{ok|Participate in driving daily B2G smoketest blockers, ensuring a timely backout of the regressing bug}}

** {{ok|Ensure that at least one RM is testing each day's B2G build, filing bugs as necessary}}

* '''Get rid of new B2G partner confusion around triage'''

** {{ok|Enable TAMs to quickly bring a partner into the triage loop, as much through documentation as possible}}

** {{ok|Refine/document the process of how each partner can block a specific bug (continued from [https://wiki.mozilla.org/Release_Management/Goals/2013Q2 Q2 2013])}}

** {{ok|Create a set of rules, expectations, and separation of responsibility for triage}}

* '''Create external pre-release populations for B2G'''

** {{ok|Meet with GP to improve quality and frequency of builds, and coordinate feedback from their customers (OEM pre-release program)}}

** {{ok|Use the reference hardware for v1.2 to build to build a pre-release population (Mozilla pre-release program)}}