You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We hold the same quality bar for community PRs as we do for team PRs.
This means PRs must have good test coverage
We should not hesitate to ask contributors to make changes to meet this bar
Small trivial changes (such as formatting) may be done by the team as part of merging
A PR from the community can be treated differently than a team PR. Specifically:
PRs from the community get a priority boost over other PRs while we are in the development part of the release cycle. This means even if the PR is not something we would otherwise work on we will still spend time on it. The motivation here is to encourage community contributions.
PRs from the community may be put on hold nearer the end of a release cycle when we are focusing on stabilizing the release.
Notes from team discussion:
PR process is:
Approved
.waiting-for-response
label along with comments asking for specific changesneeds-design
label along with comments on next stepsThe text was updated successfully, but these errors were encountered: