Skip to content

Commit 7ef2d73

Browse files
authored
Merge pull request #843 from lolbinarycat/team-roles
2 parents 1edc5e0 + 1f1b7f0 commit 7ef2d73

File tree

1 file changed

+31
-1
lines changed

1 file changed

+31
-1
lines changed

src/release/issue-triaging.md

+31-1
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ Note that some labels may only be applied by users with write access to [`rust-l
8080
There are many different labels that can be applied to issues.
8181

8282
- `needs-triage`: Signals that an issue is new and needs initial triage.
83-
- [`T-*`]: Specifies the team or teams that this issue is relevant to. For example `T-compiler`, `T-types` or `T-libs`.
83+
- [`T-*`]: Specifies the team or teams that this issue is relevant to. For example `T-compiler`, `T-types` or `T-libs`. See [Team Examples](#team-examples) for more details.
8484
- [`WG-*`]: Specifies the working groups that this issue is relevant to, for example `WG-debugging`.
8585
- [`PG-*`]: Specifies the project groups that this issue is relevant to, for example the `PG-exploit-mitigations`.
8686
- [`C-*`]: Specifies the category of the label, for example a bug, tracking issue or discussion.
@@ -145,6 +145,36 @@ There are many different labels that can be applied to issues.
145145
- An FCP will also cause a relnotes issue to be created, if it's started on an issue.
146146
- [`metabug`]: Tracks other bugs.
147147

148+
#### Team Examples
149+
This section gives a list of examples of kinds of issues that should be assigned to a specific team.
150+
151+
##### T-compiler
152+
Anything related to the compiler implementation, such as diagnostics and ICEs.
153+
154+
##### T-libs
155+
* Changes to implementation details of library functions
156+
* Spelling, grammar, and organizational changes in library docs
157+
158+
##### T-libs-api
159+
* New library apis, such as functions and methods
160+
* Changes to signatures of unstable functions
161+
* Semantic changes to library documentation,
162+
such as guaranteeing that a function will produce a certain error code in some situation
163+
* Type inference breakage due to library changes, such as new trait implementations
164+
165+
##### T-lang
166+
* New keywords/language features
167+
* Changes to the keyword docs in the standard library
168+
169+
##### T-spec
170+
* Changes to [the reference](https://github.com/rust-lang/reference/)
171+
172+
##### T-opsem
173+
* Changes to [the nomicon](https://doc.rust-lang.org/nomicon/)
174+
* Changes to the semantics of the abstract machine, such as the sematics of atomics.
175+
* Changes to the docs of unsafe pointer functions
176+
* Changes to the docs of `core::ptr`
177+
148178
### Creating labels
149179

150180
<div class="warning">

0 commit comments

Comments
 (0)