What should I work on?

This page attempts to be a one-stop shop for figuring out what the most important thing to work on is, so that team members (contributors) can determine the more effective way to improve Flutter.

1. Build breakage. Check the dashboard.
2. TODAY bugs.
3. P0 issues
4. P1 issues
5. Mentoring promising new contributors.
6. Fixing flaky tests.
7. Performance regressions. Check the dashboard. See also reported performance regressions.
8. Filed regressions.
9. Code review of open PRs.
10. Reducing technical debt. (For example, increasing our test coverage by writing new tests.)
11. Assigned bugs. We want to avoid slipping milestones, so once a bug is assigned it should also be given a named month milestone and we should ensure it's resolved by that date. See Issue Hygiene.
12. The priorities described on our roadmap, which may include:
    • P2 issues.
    • Bugs marked as annoyances.
    • Bugs labeled as issues of quality.
    • Bugs with the crash label.
13. Issues sorted by thumbs-up.
14. Everything else.

Bugs in other bug systems should be tracked with bugs in GitHub. OKRs should be reflected in the items listed above. For example, OKRs should reflect what the roadmap covers, expected customer blockers, and so forth. Work that is unique to a particular quarter would be represented by a filed bug with a milestone and assignee.

Sometimes, items in the list above escalate. For example, a performance regression might get filed as a TODAY bug and thus start trumping a customer blocker issue.

See also:

• Issue Hygiene, in particular the section on prioritization.