For people who aren't subscribed to dev-firefox, be aware that open bugs that haven't been modified in a year have been set to "inactive" without any bugmail being generated, in bug 1445054. It is probably better to that thread rather than creating a new parallel thread on this list...
Andrew ---------- Forwarded message ---------- From: Erin Lancaster <elancas...@mozilla.com> Date: Thu, May 24, 2018 at 11:52 AM Subject: Re: Bugs being resolved as INACTIVE To: Marco Bonardo <mbona...@mozilla.com>, Tom Ritter <t...@mozilla.com>, Firefox Dev <firefox-...@mozilla.org> Cc: Emma Humphries <e...@mozilla.com> Hi Everybody, Emma is out for the next few days so I want to share some information in the meantime. The spec of this "change" includes the following: 1. Introducing an ‘Inactive’ state as a bug resolution in Bugzilla 2. Moving tickets that haven’t been modified in 12 months to ‘Inactive’ 3. The query excluded P1 bugs and included Firefox-related products 4. Why did we do this? To balance the signal:noise ratio in Firefox Bugzilla searches - If this mass-modify <https://bugzilla.mozilla.org/show_bug.cgi?id=1445054> has disrupted your workflow to the point you need to a virtual ‘undo’ button, please file a ticket <https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=Administration>and we will work with you to repair your workflow. Your bugs will be back to the ‘Active’ state as quickly as possible if that is what you require. Otherwise, we can evaluate what action is needed on a case-by-case basis. - The above changes were meant to improve the way we operate and did have support across the Firefox org; however, we totally missed the mark here by surprising you and mass-modifying without warning. For that we apologize and will be certain to not let that happen in the future. - We want to be more efficient with the way we work together and ‘together’ is one of key pieces of this. I’ll be collaborating with Emma to create a larger roadmap/plan of record to give people visibility into triage/Bugzilla policy and work flow changes so you are well informed before they happen. We welcome your ongoing feedback and again apologize for the surprise. Best, Erin On Thu, May 24, 2018 at 7:48 AM, Marco Bonardo <mbona...@mozilla.com> wrote: > On Thu, May 24, 2018 at 4:34 PM, Tom Ritter <t...@mozilla.com> wrote: > >> I would :) We have a lot of P5 bugs in Anti-Fingerprinting we'd like >> to keep around. Granted, they aren't 1+ year old (yet) and they have >> had some activity on them (so they might be considered 'triaged') but >> yea, P5s would still be of interest I think. >> > > Well, on the other side the new triage process requires each new bug to > get a priority, and if we'd never resolve bugs having ANY priority, we'd > never resolve anything. Untriaged, P4 and P5 importance is low enough to be > good candidates to be automatically handled after 1 year. If they are > active it's not a big deal. There could maybe still be a way to opt-out > single bugs. > My concern was mostly about the fact P1-3 are supposed to be important > bugs that someone should be working on, and the fact we lack the resources > to do that does not lower their importance. > > > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev > > _______________________________________________ firefox-dev mailing list firefox-...@mozilla.org https://mail.mozilla.org/listinfo/firefox-dev _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
