Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

Commit de6bb34

Browse files
Remove the PR review section (#4679)
The plugins repository is now aligned with normal Flutter review process. There are no longer any open issues with the `backlog` label, and the intent is not to use it going forward due to the issues (bitrot, authors no longer being available, duplication of work) caused by leaving PRs open in limbo for a long period of time.
1 parent c2d3def commit de6bb34

File tree

1 file changed

+0
-22
lines changed

1 file changed

+0
-22
lines changed

CONTRIBUTING.md

Lines changed: 0 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -42,28 +42,6 @@ use, and use auto-formatters:
4242
- [Objective-C](https://google.github.io/styleguide/objcguide.html) formatted with
4343
`clang-format`
4444

45-
### The review process
46-
47-
Reviewing PRs often requires a non-trivial amount of time. We prioritize issues, not PRs, so that we use our maintainers' time in the most impactful way. Issues pertaining to this repository are managed in the [flutter/flutter issue tracker and are labeled with "plugin"](https://github.com/flutter/flutter/issues?q=is%3Aopen+is%3Aissue+label%3Aplugin+sort%3Areactions-%2B1-desc). Non-trivial PRs should have an associated issue that will be used for prioritization. See the [prioritization section](https://github.com/flutter/flutter/wiki/Issue-hygiene#prioritization) in the Flutter wiki to understand how issues are prioritized.
48-
49-
Newly opened PRs first go through initial triage which results in one of:
50-
* **Merging the PR** - if the PR can be quickly reviewed and looks good.
51-
* **Requesting minor changes** - if the PR can be quickly reviewed, but needs changes.
52-
* **Moving the PR to the backlog** - if the review requires non-trivial effort and the issue isn't currently a priority; in this case the maintainer will:
53-
* Add the "backlog" label to the issue.
54-
* Leave a comment on the PR explaining that the review is not trivial and that the issue will be looked at according to priority order.
55-
* **Starting a non-trivial review** - if the review requires non-trivial effort and the issue is a priority; in this case the maintainer will:
56-
* Add the "in review" label to the issue.
57-
* Self assign the PR.
58-
* **Closing the PR** - if the PR maintainer decides that the PR should not be merged.
59-
60-
Please be aware that there is currently a significant backlog, so reviews for plugin PRs will
61-
in most cases take significantly longer to begin than the two-week timeframe given in the
62-
main Flutter PR guide. An effort is underway to work through the backlog, but it will
63-
take time. If you are interested in hepling out (e.g., by doing initial reviews looking
64-
for obvious problems like missing or failing tests), please reach out
65-
[on Discord](https://github.com/flutter/flutter/wiki/Chat) in `#hackers-ecosystem`.
66-
6745
### Releasing
6846

6947
If you are a team member landing a PR, or just want to know what the release

0 commit comments

Comments
 (0)