Marking issues as regressions

Oct. 20, 2020 · Camelid on behalf of the release team

The Rust project gets many issues filed every day, and we need to keep track of them all to make sure we don't miss anything. To do that we use GitHub's issue labels feature, and we need your help to make sure we fix regressions as soon as possible!

We have many issue labels that help us organize our issues, and we have a few in particular that mark an issue as a regression. These labels will ping a Rust working group called the prioritization working group, whose members will work to determine the severity of an issue and then prioritize it. But, this won't happen unless someone marks the issue with one of those labels!

We recently had a case where a regression was not caught before a release because the issue was not marked with a regression label. So we have now added the ability for anyone to set regression labels on issues! This is all you have to do to mark an issue as a regression and it will automatically ping people to prioritize it:

@rustbot modify labels: regression-untriaged

Alternatively, if you are reporting a new regression, you can use the regression issue template. It will guide you through the process of reporting a regression and providing information that will help us fix the issue.

Finally, if you have an issue that is not a regression, but is still something that is important to be fixed, you can request prioritization with:

@rustbot prioritize

We really appreciate it if you mark all regressions with an appropriate label so we can track them and fix them as soon as possible!