mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
bec21365ce
- Adds an overview at the top about how triage works from a very high level. Right now the page discusses primary and secondary/team triage without ever actually introducing those concepts. Also sets some expectations around timelines, as we do for reviews in other docs. - Clarifies that some sub-sections of the team assignment flow chart are additional steps rather than alternate path (especially since the intro says to stop once a team assignment matches, so it was unclear that the sub-bullets applied as well). - Adds more discussion of common labels.
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 website 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
- Style guide for Flutter repo
- Submitting code, process for
- Support levels, definitions of
- Symbolicating stack traces
- Threading in the Engine
- When will my bug be fixed?
- Security best practices