Skip to content

Commit d5a6913

Browse files
committed
Add post about using regression labels
1 parent 7c73abf commit d5a6913

File tree

1 file changed

+48
-0
lines changed

1 file changed

+48
-0
lines changed
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
layout: post
3+
title: "Marking issues as regressions"
4+
author: Camelid
5+
description: "Now anyone can mark issues as regressions!"
6+
team: the release team <https://www.rust-lang.org/governance/teams/operations#release>
7+
---
8+
9+
If you've contributed to Rust before, you have likely used a command like this
10+
to [set labels][rustbot-labeling-docs]:
11+
12+
> @**rustbot** modify labels: A-typesystem C-enhancement
13+
14+
Setting labels on issues and pull requests helps us keep track of and filter
15+
issues. There are many kinds of labels you can set to mark an issue
16+
as pertinent to a particular team, related to a part of the compiler, or
17+
what kind of bug it is (a hang, a crash, etc.).
18+
19+
We also have labels that help us keep track of regressions so that we can
20+
prioritize them and fix them quickly if they are severe. We have three
21+
regression labels, each representing when the regression occurred:
22+
23+
* regression-from-stable-to-nightly
24+
* regression-from-stable-to-beta
25+
* regression-from-stable-to-stable
26+
27+
We recently had a case where a [regression was not caught][internals-thread]
28+
before a release because the issue was not marked with a regression label.
29+
So we have now [added the ability][regression-label-pr] for *anyone* to set
30+
regression labels on issues! This is all you have to do to mark an issue as a
31+
regression and it will automatically be prioritized:
32+
33+
> @**rustbot** modify labels: regression-from-stable-to-{release-channel}
34+
35+
Just replace `{release-channel}` with one of `nightly`, `beta`, or `stable`,
36+
depending on when the regression occurred, and you're good to go!
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+
Finally, if you have an issue that is *not* a regression, but is still something
42+
that is important to be fixed, you can request prioritization with:
43+
44+
> @**rustbot** prioritize
45+
46+
[rustbot-labeling-docs]: https://rustc-dev-guide.rust-lang.org/rustbot.html#issue-relabeling
47+
[internals-thread]: https://internals.rust-lang.org/t/1-46-is-unusable-for-me-solved/13161/10
48+
[regression-label-pr]: https://github.com/rust-lang/rust/pull/77555

0 commit comments

Comments
 (0)