Skip to content

Commit 9ed7709

Browse files
authored
Merge pull request #964 from apiraino/update-prio-docs
Update prioritization docs
2 parents 918d706 + 143cb85 commit 9ed7709

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

src/triagebot/requesting-prioritization.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,13 @@
11
# Requesting Prioritization
22

3-
Users can request an issue to be prioritized by the Prioritization WG.
3+
Users can request an issue to be prioritized. Prioritization means that the relevant team (T-compiler, T-rustdoc, T-libs) will have a look at the issue and assess its priority.
4+
5+
This procedure is usually reserved to *regressions*, the Rust project takes regressions seriously and these have usually priority above all the rest. When a regression is filed using the dedicated [GitHub issue template][gh-regression-tpl], a prioritization of that issue is automatically requested.
6+
7+
To learn more about this procedure, please visit the [prioritization] documentation.
8+
9+
[gh-regression-tpl]: https://github.com/rust-lang/rust/blob/master/.github/ISSUE_TEMPLATE/regression.md
10+
[prioritization]: ../compiler/prioritization.md
411

512
## Usage
613

@@ -10,9 +17,9 @@ On repositories configured for prioritization, any user can post a comment with:
1017
@rustbot prioritize
1118
```
1219

13-
which will add the `I-prioritize` label to the issue to notify the [Prioritization WG] that the issue needs prioritization.
20+
which will add the `I-prioritize` label to the issue and send a notification on [Zulip][prio-alerts].
1421

15-
[Prioritization WG]: https://www.rust-lang.org/governance/teams/compiler#Prioritization%20working%20group
22+
[prio-alerts]: https://rust-lang.zulipchat.com/#narrow/channel/245100-t-compiler.2Fprioritization.2Falerts/topic/.23147831.20Redundant.20bounds.20check.20when.20indexing.20array.20with.20enu.E2.80.A6/with/545925945
1623

1724
## Configuration
1825

0 commit comments

Comments
 (0)