Skip to content

[Merged by Bors] - Update milestone section in contributing.md #7213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from
Closed

[Merged by Bors] - Update milestone section in contributing.md #7213

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a62135f
a
BoxyUwU Jan 15, 2023
7eca4d7
use `*` not `-`
BoxyUwU Jan 15, 2023
a00766a
link to github queries for the `P-*` labels
BoxyUwU Jan 15, 2023
24829a3
a
BoxyUwU Jan 15, 2023
4e329f3
a
BoxyUwU Jan 15, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,9 +108,14 @@ Here are some useful pull request queries:
* [Uncontroversial pull requests which have been reviewed and are ready for maintainers to merge](https://github.com/bevyengine/bevy/pulls?q=is%3Aopen+is%3Apr+label%3AS-Ready-For-Final-Review+-label%3AS-Controversial+-label%3AS-Blocked+-label%3AS-Adopt-Me+)
* [Controversial pull requests which have been reviewed and are ready for final input from a Project Lead or SME](https://github.com/bevyengine/bevy/pulls?q=is%3Aopen+is%3Apr+label%3AS-Ready-For-Final-Review+label%3AS-Controversial+)

### Preparing Releases
### Prioritizing PRs and issues

We track issues and pull requests that must be included in releases using [Milestones](https://github.com/bevyengine/bevy/milestones).
We use [Milestones](https://github.com/bevyengine/bevy/milestones) to track issues and PRs that:

* Need to be merged/fixed before the next release. This is generally for extremely bad bugs i.e. UB or important functionality being broken.
* Would have higher user impact and are almost ready to be merged/fixed.

There are also two priority labels: [`P-Critical`](https://github.com/bevyengine/bevy/issues?q=is%3Aopen+is%3Aissue+label%3AP-Critical) and [`P-High`](https://github.com/bevyengine/bevy/issues?q=is%3Aopen+is%3Aissue+label%3AP-High) that can be used to find issues and PRs that need to be resolved urgently.

## Making changes to Bevy

Expand Down