Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add post about using regression labels #706

Merged
merged 3 commits into from
Oct 20, 2020
Merged

Add post about using regression labels #706

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8cacdb5
Add post about using regression labels
camelid Oct 8, 2020
41820b3
Move to main blog and future-date post date
camelid Oct 17, 2020
9d7fff1
Make more approachable to non-contributors
camelid Oct 17, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 44 additions & 0 deletions posts/2020-10-20-regression-labels.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
---
layout: post
title: "Marking issues as regressions"
description: "Now anyone can mark issues as regressions!"
author: Camelid
team: the release team <https://www.rust-lang.org/governance/teams/operations#release>
---

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*][wg-prioritization],
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][internals-thread]
before a release because the issue was not marked with a regression label.
So we have now [added the ability][regression-label-pr] 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!

[wg-prioritization]: https://rust-lang.github.io/compiler-team/working-groups/prioritization
[internals-thread]: https://internals.rust-lang.org/t/1-46-is-unusable-for-me-solved/13161/10
[regression-label-pr]: https://github.com/rust-lang/rust/pull/77555
[issue template]: https://github.com/rust-lang/rust/issues/new/choose