I've seen you started marking unassigned P1s as "stale" and stating their priority will be reset if they stay unassigned. Please don't do that, it's a very bad idea.
We are using P1s to have a list of bugs the team should be working on as soon as they have time, and there must be no strict assignee because the resources must stay flexible. I honestly don't see which benefit we'll gain by giving those bugs fake assignee, since a real one can't be given. Plus external contributors can use those list to help. P2 is a list of bugs that should be taken only once P1s are done. IT's a much larger list, so merging everything there wouldn't work. P3 is an even larger list, so moving P2s to P3s would basically make them disappear. The idea around P1 = this version, P2 = next version can work for some teams, but not all the teams have a manageable amount of bugs to track, and an approapriate number of resources to handle those, because some components (primary UI) are very much exposed to users and get a lot of bug reports. Triaging is an effort the team does, and resetting priorities would just throw all that work away. It should be acceptable that a P1 is not fixed in time for the current version (provided everyone should do its best to make it), since it's part of the "don't ship if not ready" philosophy of the rapid release process. If we really want P1s with an assignee, then we should reintroduce P4 as the backlog, so we can use P2 and P3 to prioritize their work. On Thu, Aug 24, 2017 at 1:25 AM, Emma Humphries <e...@mozilla.com> wrote: > 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. >> >> > > _______________________________________________ > Firefox-triage-leads mailing list > firefox-triage-le...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-triage-leads > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
