Difference between revisions of "Platform"
(mark me as REO for 59) |
(→Weekly Regression Triage Meeting: update to Bugzilla list of triage owners) |
||
Line 23: | Line 23: | ||
* 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 | * 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 | * 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:// | + | * in case it's necessary, here are the [https://bugzilla.mozilla.org/page.cgi?id=triage_owners.html owners associated with bugzilla components] |
=== Asynchronous Regression Tracking === | === Asynchronous Regression Tracking === |
Revision as of 00:32, 5 December 2017
This wiki page is devoted to the planning, scheduling, and documenting of meetings, discussions, and status of the Mozilla platform teams.
Contents
Planning
- See The Platform Planning Page for notes on upcoming releases and planning events. (NOTE: this used to be the Post1.9Planning Spreadsheets for all releases after 1.9.).
- See also Firefox/Namoroka#Firefox.next Platform Requirements and its talk page.
- See also the Wanted page for a few items wanted by extension/application developers
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
- Wednesdays 8-9 Pacific in ReleaseCoordination vidyo room
- REO for each active release goes through the bug queries for their release and sees if something requires a needinfo or email to a relevant party
- driving down the numbers on the Release Health Dashboard is a nice output
- in case it's necessary, here are the owners associated with bugzilla components
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 |
59 | LINK | LINK | LINK | LINK | LINK |
58 | LINK | LINK | LINK | LINK | LINK |
57 | LINK | LINK | LINK | LINK | LINK |
Regression Engineering Owner Schedule
If you can't find the person in charge of a release, slide down to the next one in the list.
- Firefox 57 - Jim Mathies
- Firefox 58 - Mike Taylor (:miketaylr)
- Firefox 59 - Andrew Overholt (:overholt)
Past Regression Engineering Owners
- Firefox 56 - Panos Astithas (:past)
- Firefox 55 - Mike Taylor (:miketaylr)
- Firefox 54 - Nathan Froyd
- Firefox 53 - Randell Jesup
- 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
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=2024-08-20 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.