8c4295b116
Currently the ecosystem team triages all PRs in the packages repository, but the platform teams also triage all PRs with their platform label. Due to the way PRs in packages work, however, it's relatively common for a PR to not be relevant to all the teams' triages at all times. Common examples: - One platform team may LGTM a multi-platform PR for their platform's portion, while another platform goes through review for several more weeks. - A cross-platform PR may not have high-level design approval from the ecosystem owner, at which point platform implementation review is premature. To avoid PRs showing up repeatedly in a platform team's triage when it's not relevant, this adjusts the triage structure: - Queries for PRs in platform teams query `triage-<platform name>` rather than `platform-<platform name>` - Ecosystem triage will add the `triage-<platform name>` label during triage when a PR is ready for that platform team's consideration. - Platform teams can remove the label when it's not relevant to them (e..g, after it's been LGTM'd for that platform). This also adds a desktop PR query, since there wasn't one, covering the separate platforms. They are separated to allow for more triage flexibility in the future.
This wiki is primarily aimed at engineers building or making contributions to Flutter.
If you are new to Flutter, then you will find more general information on the Flutter project, including tutorials and samples, on our Web site at flutter.dev. For specific information about Flutter's APIs, consider our API reference which can be found at the api.flutter.dev.
If you want to know what we're likely to do in the future, our roadmap may be of interest.
If you intend to contribute to Flutter, welcome! You are encouraged to start with our contributor guide, which helps onboard new team members. It points to the most relevant pages on this wiki. You are also invited to join our Discord server.
Index of notable sections
- Actionable bugs, and the closing of unactionable bugs
- Breaking changes
- Cherrypick process
- Closing issues
- Dashboards
- Debugging a broken engine autoroll
- Deprecations
- Design documents
- Discord
- Engineering Philosophy
- Flaky tests
- flutter.dev is down
- Issue prioritization
- Labels
- Milestones
- Plugin compatibility policy
- Reviewing code
- RFC process
- Status of popular issues
- Submitting code, process for
- Support levels, definitions of
- Symbolicating stack traces
- Threading in the Engine
- When will my bug be fixed?
- Security best practices