{"id":3683,"date":"2012-11-15T19:13:53","date_gmt":"2012-11-15T19:13:53","guid":{"rendered":"http:\/\/blog.mozilla.org\/websites\/?p=13"},"modified":"2014-06-02T14:50:13","modified_gmt":"2014-06-02T22:50:13","slug":"mozilla-org-bug-triage-process","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/webdev\/2012\/11\/15\/mozilla-org-bug-triage-process\/","title":{"rendered":"Mozilla.org bug triage process"},"content":{"rendered":"

The list of open bugs for Mozilla.org has grown to an overwhelming 1,200+ bugs<\/a> . This large number of open bugs interferes with our ability to guarantee that we are fixing the most mission critical bugs in a timely manner.\u00a0 As a result, we propose the following process to reduce the signal to noise ratio.<\/p>\n

What:<\/h2>\n

Manage the mozilla.org bug list by meeting regularly to prioritize and close bugs, as appropriate.<\/p>\n

Why:<\/h2>\n

The mozilla.org open bug list has grown to a nearly unmanageable size. In order to ensure we are aware of the most urgent bugs and prioritizing our time and resources against the most important bugs, we will begin to meet regularly to review, prioritize, and close bugs. We hope this will result in urgent bugs getting fixed more quickly, more efficient use of team resources, and clear communication regarding bug status, including reasons why some bugs may receive a “closed\/won’t fix” status.<\/p>\n

Who:<\/h2>\n

Mozilla.org product manager (me) and project manager (Mike Alexis) plus other interested parties.\u00a0 If anyone would like to join us in this process, please let me know!\u00a0 We can always use additional help reviewing and prioritizing open bugs.<\/p>\n

When:<\/h2>\n

Every other Thursday (11am Pacific) at first then monthly once the number of open bugs decreases below<\/p>\n

Where:<\/h2>\n