mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
08a7ec79b5
_The following applies only to PRs in `flutter/packages`_ After speaking with @stuartmorgan-g, updating the team-web PR triage links to align with the expectations of the ecosystem team: 1. The ecosystem team does a first pass triage and adds `triage-*` labels to request review from other teams. 2. The web team reviews PRs labelled with `triage-web`. 3. The web team removes the `triage-web` label when they approve the PR and don't need to look at it anymore. 4. If the web team is the last reviewer, they should apply the `autosubmit` label.
2.6 KiB
2.6 KiB
When triaging web issues follow the following process:
- Make sure there are no unassigned P0 and P1 issues.
- Make sure there are no P1 issues outside the backlog.
- Make sure there are no P3 issues in the backlog.
- Make sure there are no assigned P2 and P3 issues (if you'd like to become a regular Flutter Web contributor, please ping yjbanov on Discord to be added to this list, and we'll watch that your issues are properly triaged):
- All P0 issues are assigned and being worked on.
- The list of P1 issues should be manageable (<30 issues)
- Number of open PRs should be manageable (<15):
- flutter/flutter
- flutter/packages
- Remove the
triage-weblabel when the PR is approved. - If you are the last reviewer, add the
autosubmitlabel.
- Remove the
- Triage untriaged issues