September 6th, 2017
wild_irises: (reading)
September 5th, 2017
emceeaich: A woman in glasses with grey hair, from the eyes up, wearing a hairband with 'insect antenna' deelie-boppers (bugmaster)
posted by [personal profile] emceeaich at 06:13pm on 05/09/2017 under , ,

It's the weekly report on the state of triage in Firefox-related components.

Marking Bugs for the Firefox 57 Release

The bug that will overshadow all the hard work we put into the Firefox 57 release has probably already been filed. We need to find it and fix it. If you think a bug might affect users in the 57 release, please set the correct Firefox versions affected in the bug, and then set the tracking-request flag to request tracking of bug by release management team.

Poll Result

It’s not a large sample, but by an 8-1-1 margin, you said you’d like a logged-in BMO home page like: https://fitzgen.github.io/bugzilla-todos/.

Now, the catch. We don’t have staff to work on this, but I’ve filed a bug, https://bugzilla.mozilla.org/show_bug.cgi?id=1397063 to do this work. If you’d like undying gratitude, and some WONTFIX swag, grab this bug.

Hotspots

The components with the most untriaged bugs remain the JavaScript Engine and Build Config.

**Rank**   **Component**                  **Last Week**   **This Week**
---------- ------------------------------ --------------- ---------------
1          Core: JavaScript Engine        477             472
2          Core: Build Config             459             455
3          Firefox for Android: General   408             415
4          Firefox: General               254             258
5          Core: General                  241             235
6          Core: JavaScript: GC           180             175
7          Core: XPCOM                    171             172
8          Core: Networking               159             167
           All Components                 8,822           8,962

Please make sure you’ve made it clear what, if anything will happen with these bugs.

Not sure how to triage? Read https://wiki.mozilla.org/Bugmasters/Process/Triage.

Next Release

**Version**                           56      56    57     57      57      57
------------------------------------- ------- ----- ------ ------- ------- -------
**Date**                              7/31    8/7   8/14   8/21    8/21    9/5
**Untriaged this Cycle**              4,479   479   835    1,196   1,481   1,785
**Unassigned Untriaged this Cycle**   3,674   356   634    968     1,266   1,477
**Affected this Release**             139     125   123    119     42      83
**Enhancements**                      103     3     5      11      17      15
**Orphaned P1s**                      192     196   191    183     18      23
**Stalled P1s**                       179     157   152    155     13      23

What should we do with these bugs? Bulk close them? Make them into P3s? Bugs without decisions add noise to our system, cause despair in those trying to triage bugs, and leaves the community wondering if we listen to them.

Methods and Definitions

In this report I talk about bugs in Core, Firefox, Firefox for Android, Firefox for IOs, and Toolkit which are unresolved, not filed from treeherder using the intermittent-bug-filer account*, and have no pending needinfos.

By triaged, I mean a bug has been marked as P1 (work on now), P2 (work on next), P3 (backlog), or P5 (will not work on but will accept a patch).

https://wiki.mozilla.org/Bugmasters#Triage_Process

A triage decision is not the same as a release decision (status and tracking flags.)

https://mozilla.github.io/triage-report/#report

Untriaged Bugs in Current Cycle

Bugs filed since the start of the Firefox 57 release cycle (August 2nd, 2017) which do not have a triage decision.

https://mzl.la/2wzJxLP

Recommendation: review bugs you are responsible for (https://bugzilla.mozilla.org/page.cgi?id=triage_owners.html) and make triage decision, or RESOLVE.

Untriaged Bugs in Current Cycle Affecting Next Release

Bugs marked status_firefox56 = affected and untriaged.

https://mzl.la/2wzjHaH

Enhancements in Release Cycle

Bugs filed in the release cycle which are enhancement requests, severity = enhancement, and untriaged.

https://mzl.la/2wzCBy8

​Recommendation: ​product managers should review and mark as P3, P5, or RESOLVE as WONTFIX.

High Priority Bugs without Owners

Bugs with a priority of P1, which do not have an assignee, have not been modified in the past two weeks, and do not have pending needinfos.

https://mzl.la/2sJxPbK

Recommendation: review priorities and assign bugs, re-prioritize to P2, P3, P5, or RESOLVE.

Inactive High Priority Bugs

There 159 bugs with a priority of P1, which have an assignee, but have not been modified in the past two weeks.

https://mzl.la/2u2poMJ

Recommendation: review assignments, determine if the priority should be changed to P2, P3, P5 or RESOLVE.

Stale Bugs

Bugs in need of review by triage owners. Updated weekly.

https://mzl.la/2wNyONP

* New intermittents are filed as P5s, and we are still cleaning up bugs after this change, See https://bugzilla.mozilla.org/show_bug.cgi?id=1381587, https://bugzilla.mozilla.org/show_bug.cgi?id=1381960, and https://bugzilla.mozilla.org/show_bug.cgi?id=1383923

If you have questions or enhancements you want to see in this report, please reply to me here, on IRC, or Slack and thank you for reading.

April

SunMonTueWedThuFriSat
          1
 
2
 
3
 
4
 
5
 
6
 
7 8
 
9
 
10
 
11
 
12
 
13
 
14
 
15
 
16
 
17
 
18
 
19
 
20
 
21
 
22
 
23
 
24
 
25
 
26
 
27
 
28
 
29
 
30