Platform: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(updated 57)
(Reorganize and rename "Engineering Release Boss" sections)
Line 7: Line 7:


== Bug Triage ==
== 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:
* 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);
** 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;
** 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
** ?: 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 ====
==== Crash Bug Triage ====

Revision as of 19:25, 6 June 2017

This wiki page is devoted to the planning, scheduling, and documenting of meetings, discussions, and status of the Mozilla platform teams.

Planning

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 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

Asynchronous Regression Tracking

  • 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);
    • wontfix: we will not take a fix for this regression in this particular release;
    • 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

Crash Bug Triage

  • 1-10 position in release: needs an owner, tracking release, needs a fix
  • 11-30 position in release: needinfo component owner looking for an owner to investigate
  • 31-50 position in release: case-by-case, mostly fix-optional
  • Above 50: mark as fix-optional
  • Check for exploitability - you may want to file the bug as security sensitive

Bugzilla Queries

General Queries

Created Last 90 Days

Modified Last 90 Days

Flagged Bugs

New Regressions

Criteria

Keywords regression
status-firefox (this version) affected
status-firefox (previous version) unaffected, implying this is a new regression
tracking-firefox (this version) not "-" (tracked or untriaged)


Carry Over Regressions

Criteria

Keywords regression
status-firefox (this version) affected
status-firefox (previous version) affected (or related)
tracking-firefox (this version) not "-" (tracked or untriaged)

Bug Lists

Version New Bugs New w/Needinfos Carry Over Carry Over w/Needinfos Fixed Bug "Burndown" List
55 LINK LINK LINK LINK LINK
54 LINK LINK LINK LINK LINK
53 LINK LINK LINK LINK LINK

Engineering Release Boss Schedule

If you can't find the person in charge of a release, slide down to the next one in the list.

  • Firefox 53 - Randell Jesup
  • Firefox 54 - Nathan Froyd
  • Firefox 55 - Michael Taylor (:miketaylr)
  • Firefox 56 - ?
  • Firefox 57 - Jim Mathies

Past Bosses

  • Firefox 52 - Ryan VanderMeulen
  • Firefox 51 - Milan Sreckovic
  • Firefox 50 - Andrew Overholt
  • Firefox 49 - David Bolter
  • Firefox 48 - James Willcox
  • Firefox 47 - Jim Mathies
  • Firefox 46 - Jim Mathies

Platform Team Goals

Main article: Platform/Roadmap
2015 Q1 Goals Q2 Goals Q3 Goals Q4 Goals
2014 Q1 Goals Q2 Goals Q3 Goals Q4 Goals
2013 Q1 Goals Q2 Goals Q3 Goals Q4 Goals
2012 Q1 Goals Q2 Goals Q3 Goals Q4 Goals
2011 Q1 Goals Q2 Goals Q3 Goals Q4 Goals
2010 Q1 Goals Q2 Goals Q3 Goals Q4 Goals
2009 Q1 Goals Q2 Goals Q3 Goals Q4 Goals
2008 Q1 Goals Q2 Goals Q3 Goals Q4 Goals
2007 - Q2 Goals Q3 Goals Q4 Goals

Meeting Notes

Create a new weekly agenda from the template: <createbox> align=left type=create preload=Platform/0-0-0 default=2025-12-16 prefix=Platform/ </createbox>

2015

2014

2013

2012

2011

2010

2009

2008

2007

Mozilla Platform Functional Groups

Some teams have their own meetings during the week to discuss specific issues:


Platform Active Projects

Current major feature or initiatives in Platform

All Platform pages

Visit Special:PrefixIndex/Platform/ to see all subpages of "Platform" on wiki.mozilla.org.

Retrieved from "https://wiki.mozilla.org/index.php?title=Platform&oldid=1172818"