If you’ve ever taken a look at Flutter’s Issues on GitHub, you’ve probably noticed the abundance of labels—some instantly understandable, others not so much. The ones that tend to be confusing are mostly Triage labels, namely P0, P1, P2, P3, P4, P5, and P6. In this post, we’ll go through what each of these means, whether you’re curious about what’s coming in Flutter’s near-future Next Release or interested in contributing to Flutter.
P0, P1, P2, P3
These can be thought of as Critical Issues affecting Flutter’s Core Engine, categorized by severity as follows:
P0
P0 represents the most severe problems—those causing Core Engine crashes, affecting a large number of users, and requiring immediate fixes.
P1
P1 covers serious issues needing urgent attention, though not as critical as P0. These are scheduled for resolution as soon as possible (typically the current milestone), with status updates required within two weeks.
P2
P2 is used for tracking all bugs that have been formally scheduled for a specific timeframe (assigned to a milestone).
P3
P3 serves as a filter for issues triaged up from P4 that are deemed important or necessary.
P4, P5, P6
Issues in this group are non-critical, haven’t yet been assessed for severity, or are feature requests of various kinds.
P4
P4 is for bugs that don’t severely impact functionality and are slated for future fixes.
P5
P5 is used for feature requests.
P6
P6 is for feature requests that don’t align with the roadmap and aren’t likely to be implemented anytime soon.
Beyond these main labels, Flutter has many others. Those interested in the full details can check out the Flutter Wiki.
📚 Hope you enjoy reading!