Correcting some links at the bottom of this report:

*Untriaged Bugs in Current Cycle*

Bugs filed since the start of the Firefox 57 release cycle 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*](https://bugzilla.mozilla.org/page.cgi?id=triage_owners.html)
)
and make triage decision, or RESOLVE.

*Untriaged Bugs in Current Cycle (57) Affecting Next Release (56)*

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

On Mon, Aug 21, 2017 at 4:01 PM, Emma Humphries <e...@mozilla.com> wrote:

> It's the weekly report on the state of triage in Firefox-related
> components. I apologize for missing last week’s report. I was travelling
> and did not have a chance to sit down and focus on this.
>
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to