It's the weekly report on the state of triage in Firefox-related components.
Poll Would you like a logged in BMO home page like: https://fitzgen.github.io/bugzilla-todos/? https://twitter.com/triagegirl/status/902327322178609153 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 471 477 2 Core: Build Config 450 459 3 Firefox for Android: General 406 408 4 Firefox: General 246 254 5 Core: General 235 241 6 Core: XPCOM 178 180 7 Core: JavaScript: GC 168 171 8 Core: Networking 161 159 All Components 8,703 8,822 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 Date 7/31 8/7 8/14 8/21 8/28 Untriaged this Cycle 4,479 479 835 1,196 1,481 Unassigned Untriaged this Cycle 3,674 356 634 968 1,266 Affected this Release 139 125 123 119 42 Enhancements 103 3 5 11 17 Orphaned P1s 192 196 191 183 18 Inactive P1s 179 157 152 155 13 Stale Bugs – – – – 117 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. Bugs I Want to Close There are over 10,000 unconfirmed bugs with no activity in at least a year. https://mzl.la/2wNLrbS There are over 45,000 bugs which are not in the General or Untriaged components with no activity in at least a year. https://mzl.la/2wNXiGC I would like to close these. Once the noise-free closing script is ready, my plan is to automate bug stewardship. 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 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
