You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/release/issue-triaging.md
+31-1
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ Note that some labels may only be applied by users with write access to [`rust-l
80
80
There are many different labels that can be applied to issues.
81
81
82
82
-`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.
84
84
-[`WG-*`]: Specifies the working groups that this issue is relevant to, for example `WG-debugging`.
85
85
-[`PG-*`]: Specifies the project groups that this issue is relevant to, for example the `PG-exploit-mitigations`.
86
86
-[`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.
145
145
- An FCP will also cause a relnotes issue to be created, if it's started on an issue.
146
146
-[`metabug`]: Tracks other bugs.
147
147
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.
0 commit comments