From fae28448e3571ded2c24c51af0f5d6b894a38ab7 Mon Sep 17 00:00:00 2001 From: Kenzie Davisson <43759233+kenzieschmoll@users.noreply.github.com> Date: Tue, 26 Nov 2024 15:26:11 -0800 Subject: [PATCH] Update triage instructions (#8563) --- TRIAGE.md | 48 ++++++++++++++++++++++++++++++++---------------- 1 file changed, 32 insertions(+), 16 deletions(-) diff --git a/TRIAGE.md b/TRIAGE.md index fe4d06f3458..d7ed44be71e 100644 --- a/TRIAGE.md +++ b/TRIAGE.md @@ -2,29 +2,40 @@ ## The Process -DevTools issues are triaged as time allows throughout the week, and during a dedicated triage meeting that occurs weekly. -During the triage meeting, new and existing issues are categorized, prioritized, and / or commented on to provide updates -or gather clarification. +DevTools issues are triaged weekly as time allows or at a dedicated time set aside by the triager. +The triager is assigned by an automatic rotation of DevTools team members. -The DevTools discord [channel](https://discord.com/channels/608014603317936148/958862085297672282) is also scrubbed for -any recent user questions / concerns that require a response. +## Quick links +- [Untriaged issues](https://github.com/flutter/devtools/issues?q=is%3Aopen+is%3Aissue+-label%3AP0%2CP1%2CP2%2CP3) +- [Reproduce to verify issues](https://github.com/flutter/devtools/labels/reproduce%20to%20verify) +(issues that need to be manually reproduced in order to verify validity) +- [flutter/flutter issues related to DevTools](https://github.com/flutter/flutter/labels/d%3A%20devtools) -## DevTools Issues +## Triager responsibilities -Queue: https://github.com/flutter/devtools/issues?q=is%3Aopen+is%3Aissue+-label%3AP0%2CP1%2CP2%2CP3 +The triager should spend about ~1 hour per week on maintaining the health of the DevTools repository. -For each issue, perform all of these tasks that apply: +1. Triage any [new flutter/devtools issues](https://github.com/flutter/devtools/issues?q=is%3Aopen+is%3Aissue+-label%3AP0%2CP1%2CP2%2CP3) +by applying [proper labels](#label-the-issue) and [assigning priority](#prioritize-the-issue). +2. Triage any new [flutter/flutter issues related to DevTools](https://github.com/flutter/flutter/labels/d%3A%20devtools). +Transfer any issues to the `flutter/devtools` repo that should be tracked on our own issue tracker, and close issues you +find that are obsolete. +3. Spend at least 20 minutes [cleaning up the issue backlog](#clean-up-the-issue-backlog). +4. Look through the DevTools discord [channel](https://discord.com/channels/608014603317936148/958862085297672282) for any recent user +questions or concerns that require a response. -### Label/project the issue: -* Add labels for its proper category or categories ( “Inspector page”, “debugger page”, “bug”, etc.) +### Label the issue + +* Add labels for its proper category or categories ( “screen: inspector", “screen: network", “bug”, etc.) +* Add cost labels ("cost: low", "cost: medium", etc.) if you have a good idea of how much work it will +take to resolve this issue. Leave the cost label off if you do not know. * Add label “waiting for customer response” if you requested more details from reporter * Add label “fix it friday” if the issue should be fixed and looks easy to fix * Add label "good first issue" if the issue looks like an easy starter bug for a new contributor -### Prioritize the issue. +### Prioritize the issue Follow the prioritization rubric [here](https://github.com/flutter/flutter/blob/master/docs/contributing/issue_hygiene/README.md#priorities). - If the issue requires specific expertise, tag a product area owner (see below) in a comment and ask them to take a look. If the issue is actively being worked on or if it needs immediate / almost-immediate attention (P0, P1), assign the issue to a product area owner. @@ -45,9 +56,14 @@ Here are some suggested owners by product area: For anything else that requires immediate attention but does not fit into one of the above areas, please tag @kenzieschmoll or @elliette. -## Related Flutter Issues +**Ping the [hackers-devtools](https://discord.com/channels/608014603317936148/1106667330093723668) discord channel +about issues marked “severe: …” or “P0”.** -flutter/flutter issues relating to DevTools: -https://github.com/flutter/flutter/issues?q=is%3Aopen+label%3A%22d%3A+devtools%22+++no%3Amilestone+ +### Clean up the issue backlog -Ping the [hackers-devtools](https://discord.com/channels/608014603317936148/1106667330093723668) discord channel about issues marked “severe: …” or “P0”. +This step is to ensure the health of the [DevTools issue backlog](https://github.com/flutter/devtools/issues) over time. +There are a couple of things to do as part of the backlog clean up work: +- Close any obsolete issues. Recommendation: start with the oldest issues first since these are the most likely to be stale. +- Add good candidates for product excellence / quality work to the +[DevTools Product Excellence project](https://github.com/orgs/flutter/projects/157). This project feeds monthly milestone +planning for ongoing P.E. work.