Tooling and reporting changes

[Emma Humphries]

Hi, thank you all for your questions and comments on the changes to the
triage process starting this Monday with the next merge. I want to
acknowledge that we're asking to accommodate this during a time of
uncertainty, but this will help us attain our goal of build quality.

I wanted to let you know about some changes to tooling coming up:

First, if you use https://mozilla.github.io/triage-center, it'll no longer
be supported and I'm taking the site down because of the changes to what we
consider triaged.

Second, we'll be updating arewetriagedyet.org to reflect the new triage
standard.

Lastly, if you have editbugs and are the triage owner for one or more
components, there's a query saved to Bugzilla for you "Untriaged Bugs
(Severity Based)"

AutoNag changes are being worked on, and so are the triage documentation
in-tree.

If you want to refresh yourself on the change, the document on it is here:
https://docs.google.com/document/d/1HYPBDePvYX26JOrk6ymsEeViwTdWhCVL-elSwInsMKw/

Stay safe and in good health,

Emma

[Kartikaya Gupta]

With this new triage query, a bug like
https://bugzilla.mozilla.org/show_bug.cgi?id=1633584 is considered
untriaged, because it doesn't have any of the status-firefoxXX flags
set. However it's an "enhancement" type bug and so those flags don't
really make much sense to be setting. Is this intentional, or can this
part of the query be revisited so that the status-firefoxXX flags
don't need to be set on enanchement/task bugs?

[Emma Humphries]

That should be triaged as severity = n/a, and I'll make sure the triage
definition is clear that if the severity is n/a then the status_firefoxNN
flags do not need to be set.

Thanks for calling it out!

-- Emma

[Emma Humphries]

That's arewetriagedyet.net, not. org.

Sorry for the confusion.

-- Emma