Platform: Difference between revisions

Platform (view source)

Revision as of 19:25, 6 June 2017

360 bytes removed , 6 June 2017

Reorganize and rename "Engineering Release Boss" sections

Overholt

canmove, Confirmed users

901

edits

@@ Line 7: / Line 7: @@
 == Bug Triage ==
+=== Regression Engineering Owner (REO) ===
+Every release has an assigned Regression Engineering Owner (formerly known as "Engineering Release Boss") whose responsibilities include:
+* be a partner for release management's [https://wiki.mozilla.org/Release_Management/Release_owners Release Manager] assigned to the same release
+* ensure a decision is made about each regression reported in the release
+** push for the responsible team to fix it
+** back related changes out
+** ship with it
+** delay shipping
+* keep a mental state of how we are doing with regressions in a release
+* pay close attention to release-drivers mailing list
+* run the [[#Weekly Regression Triage Meeting|weekly regression triage meeting]]
-=== Overview ===
+=== Weekly Regression Triage Meeting ===
-During the release of Firefox 45 (e.g., 46 was on Beta), we explicitly focused on reducing a number of Firefox regressions (new in particular) that we ship with each release.  A weekly meeting was convened, with the goal of triaging and resolving such regressions.  As a result of this program, the number of new regressions we shipped in 46 was zero.  (Should add the numbers for the previous releases, but they were nowhere near zero.)
+* Wednesdays 11-12 Pacific in ReleaseCoordination vidyo room
+* REO for each active release goes through the [[#Bug_Lists|bug queries]] for their release and sees if something requires a needinfo or email to a relevant party
+* driving down the numbers on the [http://mozilla.github.io/releasehealth/ Release Health Dashboard] is a nice output
+* in case it's necessary, here are the [https://docs.google.com/spreadsheets/d/10i30CFUPJM7snz0xX3czFJeBh2tNwjwjtI409DQw3x0/edit#gid=1391890455 owners associated with bugzilla components]
-=== Process ===
+=== Asynchronous Regression Tracking ===
-The process is work in progress, and may change as we go along, but currently looks something like this.
-==== Actors ====
-* An Engineering Release Boss is assigned to each release, tasked with making sure things keep running, and we have nothing falling between the cracks.
-* The [https://wiki.mozilla.org/Release_Management/Release_owners Release Manager] assigned to the same release is a critical partner.
-* A triage meeting happens on Wednesdays, 11-12 PST, in ReleaseCoordination vidyo room
-* [https://docs.google.com/spreadsheets/d/10i30CFUPJM7snz0xX3czFJeBh2tNwjwjtI409DQw3x0/edit#gid=1391890455 Owners associated with bugzilla components]
-* Gecko and Firefox engineering managers
-* Gecko and Firefox engineering directors
-* Bugzilla queries (see below) and [http://mozilla.github.io/releasehealth/ Release Health Dashboard]
-==== Play ====
 * Engineering managers and component owners keep track of regressions, especially the new ones.  They look through the list for bugs in their components and set the tracking flags for a particular release to reflect their plans for the bug, leaving an explanation in the bug when the status is changed:
 ** affected: this regression should be fixed in this particular release (it must be assigned);
@@ Line 29: / Line 31: @@
 ** fix-optional: we will take a fix if one appears, but otherwise it will go unfixed in this release;
 ** ?: we should talk about this bug in triage
-* Engineering Release Boss (ERB) looks for regressions that are not showing the signs of activity from the above group, and makes sure it happens.  They will not look at wontfix or fix-wanted bugs, except to look for potential serious issues that get misinterpreted.
-* ERB chairs the triage meeting, going through the bugs in an ordered determined in that meeting.
 ==== Crash Bug Triage ====