It's the weekly report on the state of triage in Firefox-related
components. I’m writing this from a cafe in Helsink where the sun just came
out.

Hotspots

The components with the most untriaged bugs remain the JavaScript Engine
and Build Config. It is great to see the number of untriaged bugs in Core:
Graphics drop by half. Thank you, Milan. But JavaScript Engine, y’all need
to do something with all your untriaged bugs. Are these bugs generated by
automation like the intermittent test failure bugs?

Rank

Component

Last Week

This Week

1

Core: JavaScript Engine

446

449

2

Core: Build Config

421

429

3

Firefox for Android: General

410

411

4

Core: General

239

234

5

Firefox: General

238

242

6

Core: XPCOM

178

176

7

Core: Disability Access APIs

162

159

8

Core: Graphics

194

91

All Components

8,543

8,373

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

55

55

55

55

56

Date

2017-07-10

2017-07-17

2017-07-24

2017-07-31

2017-07-31

Untriaged this Cycle

4,525

4,451

4,317

4,479

479

Unassigned Untriaged this Cycle

3,742

3,682

3,517

3,674

356

Affected this Cycle

111

126

139

125

Enhancements

102

107

91

103

3

Orphaned P1s

199

193

183

192

196

Stalled P1s

195

173

159

179

157

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.

Note

I’m traveling from the 1st to the 17th. I plan to send out updates on the
7th and 14th, but they may be delayed.

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

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

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

Age of Untriaged Bugs

The average age of a bug filed since June 1st of 2016 which has gone
without triage.

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

Untriaged Bugs in Current Cycle

Bugs filed since the start of the Firefox 55 release cycle (March 6th,
2017) which do not have a triage decision.

https://mzl.la/2u1R7gA

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/2u2GCcG

Enhancements in Release Cycle

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

​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/2u1VLem

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

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

* 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=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.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to