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 more links to issue-triaging.md #720

Merged
merged 1 commit into from
Dec 27, 2023
Merged

Add more links to issue-triaging.md #720

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 6 additions & 2 deletions src/release/issue-triaging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,13 +30,13 @@ It's okay if not all of these are always considered; treat it as a guideline, no

- The issue should make sense, that is, it should present a problem.
- For example, if an issue is a question about Rust in general, the issue should be closed and the user redirected to URLO/Discord.
You can of course answer the question too :) (but make sure to mention that the user should go to URLO/Discord next time).
You can of course answer the question too :) (but make sure to mention that the user should go to [URLO]/[Discord] next time).
- Add appropriate labels ([Labels](#labels))
- Specifically, `T-*` and `C-*` are the most relevant
- If the issue contains no reproduction but needs one, ask for one and add the `S-needs-repro` label
- The issue is the wrong place for some kinds of feature requests. Tell the author about it.
- Library API requests should follow [its processes](https://std-dev-guide.rust-lang.org/development/feature-lifecycle.html).
- Language changes should be redirected to [IRLO](https://internals.rust-lang.org/) or Zulip (t-lang).
- Language changes should be redirected to [IRLO] or Zulip ([t-lang](https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang)).
- If the issue could benefit from bisecting the regression, add `E-needs-bisection` (or do the bisection yourself)
- Does this issue require nightly? Add `requires-nightly`.
- Is the issue a regression? Apply the `regression-untriaged` label (or figure out what regression it is exactly)
Expand All @@ -50,6 +50,10 @@ For example, `@rustbot label +T-compiler +C-bug +A-linkage +O-macos -needs-triag

To see a list of all labels, check out the "labels" page next to the search bar in the issue tracker.

[URLO]: https://users.rust-lang.org
[IRLO]: https://internals.rust-lang.org/
[Discord]: https://discord.gg/rust-lang
Noratrieb marked this conversation as resolved.
Show resolved Hide resolved

## Further triaging

For issues that have been through the initial triaging step (that is, don't have the `needs-triage` label anymore), there are usually
Expand Down