Skip to content

Commit fbc52bc

Browse files
Merge pull request #706 from camelid/regression-labels
Add post about using regression labels
2 parents ca53864 + 9d7fff1 commit fbc52bc

File tree

1 file changed

+44
-0
lines changed

1 file changed

+44
-0
lines changed

posts/2020-10-20-regression-labels.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
layout: post
3+
title: "Marking issues as regressions"
4+
description: "Now anyone can mark issues as regressions!"
5+
author: Camelid
6+
team: the release team <https://www.rust-lang.org/governance/teams/operations#release>
7+
---
8+
9+
The Rust project gets many issues filed every day, and we need to keep track
10+
of them all to make sure we don't miss anything. To do that we use GitHub's
11+
issue labels feature, and we need your help to make sure we fix regressions
12+
as soon as possible!
13+
14+
We have many issue labels that help us organize our issues, and we have a few
15+
in particular that mark an issue as a regression. These labels will ping a Rust
16+
working group called the [*prioritization working group*][wg-prioritization],
17+
whose members will work to determine the severity of an issue and then
18+
prioritize it. But, this won't happen unless someone marks the issue with one
19+
of those labels!
20+
21+
We recently had a case where a [regression was not caught][internals-thread]
22+
before a release because the issue was not marked with a regression label.
23+
So we have now [added the ability][regression-label-pr] for *anyone* to set
24+
regression labels on issues! This is all you have to do to mark an issue as a
25+
regression and it will automatically ping people to prioritize it:
26+
27+
> **@rustbot** modify labels: regression-untriaged
28+
29+
Alternatively, if you are reporting a new regression, you can use the regression
30+
[issue template]. It will guide you through the process of reporting a
31+
regression and providing information that will help us fix the issue.
32+
33+
Finally, if you have an issue that is *not* a regression, but is still something
34+
that is important to be fixed, you can request prioritization with:
35+
36+
> **@rustbot** prioritize
37+
38+
We really appreciate it if you mark all regressions with an appropriate label
39+
so we can track them and fix them as soon as possible!
40+
41+
[wg-prioritization]: https://rust-lang.github.io/compiler-team/working-groups/prioritization
42+
[internals-thread]: https://internals.rust-lang.org/t/1-46-is-unusable-for-me-solved/13161/10
43+
[regression-label-pr]: https://github.com/rust-lang/rust/pull/77555
44+
[issue template]: https://github.com/rust-lang/rust/issues/new/choose

0 commit comments

Comments
 (0)