-
Notifications
You must be signed in to change notification settings - Fork 345
Triage
If you are the devtools triage rotation on-call, you are expected to triage issues that appeared/updated during the week (it is ok to triage all of them at the end of the week).
You are also expected to monitor the DevTools discord channel for user questions / concerns.
For each new issue that comes in, perform all of these tasks that apply:
- Add labels for its proper category or categories ( “Inspector page”, “debugger page”, “bug”, etc.)
- 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 to project go/dart-devtools-ux-issues if the issue is cross-screen issue
Prioritize the issue. Follow the prioritization rubric here. In summary, the priorities are as follows:
- P0 - "The world is on fire." These are rare, normally there should be zero.
- P1 - Deserves immediate attention (blocking a top tier customer, critical infra issue).
- P2 - about to block a top-tier customer or an important item of technical debt that we want to fix as soon as possible. These issues are top-of-mind and we explicitly consider them weekly.
- P3 - high-priority issues that are at the top of the work list. Actively being worked on.
- P4 - important to work on, but not at the top of the work list. This is the default level for bugs. On deck issues.
- P5 - valid but not important. This is the default level for new feature requests. Backlog issues.
- P6 - valid issues that are unlikely to ever be worked on
Tag the area owner in a comment if the issue requires specific expertise. Assign to an owner if the issue is a work in process or if the issue needs immediate / almost-immediate attention (P0, P1, P2).
flutter/flutter issues relating to DevTools: https://github.com/flutter/flutter/issues?q=is%3Aopen+label%3A%22d%3A+devtools%22+++no%3Amilestone+
Ping the chat “DevTools” about issues marked “severe: …” or “P0”.