@@ -310,10 +310,19 @@ currently. Between writing new lints, fixing issues, reviewing pull requests and
310310responding to issues there may not always be enough time to stay on top of it
311311all.
312312
313- Our highest priority is fixing [crashes][l-crash] and [bugs][l-bug]. We don' t
313+ Our highest priority is fixing [crashes][l-crash] and [bugs][l-bug], for example
314+ an ICE in a popular crate that many other crates depend on. We don' t
314315want Clippy to crash on your code and we want it to be as reliable as the
315316suggestions from Rust compiler errors.
316317
318+ We have prioritization labels and a sync-blocker label, which are described below.
319+ - [P-low][p-low]: Requires attention (fix/response/evaluation) by a team member but isn' t urgent.
320+ - [P-medium][p-medium]: Should be addressed by a team member until the next sync.
321+ - [P-high][p-high]: Should be immediately addressed and will require an out-of-cycle sync or a backport.
322+ - [L-sync-blocker][l-sync-blocker]: An issue that "blocks" a sync.
323+ Or rather: before the sync this should be addressed,
324+ e.g. by removing a lint again, so it doesn' t hit beta/stable.
325+
317326# # Bors and Homu
318327
319328We use a bot powered by [Homu][homu] to help automate testing and landing of pull
@@ -327,6 +336,10 @@ commands [here][homu_instructions].
327336[triage]: https://forge.rust-lang.org/release/triage-procedure.html
328337[l-crash]: https://github.com/rust-lang/rust-clippy/labels/L-crash
329338[l-bug]: https://github.com/rust-lang/rust-clippy/labels/L-bug
339+ [p-low]: https://github.com/rust-lang/rust-clippy/labels/P-low
340+ [p-medium]: https://github.com/rust-lang/rust-clippy/labels/P-medium
341+ [p-high]: https://github.com/rust-lang/rust-clippy/labels/P-high
342+ [l-sync-blocker]: https://github.com/rust-lang/rust-clippy/labels/L-sync-blocker
330343[homu]: https://github.com/rust-lang/homu
331344[homu_instructions]: https://bors.rust-lang.org/
332345[homu_queue]: https://bors.rust-lang.org/queue/clippy
0 commit comments