about summary refs log tree commit diff
path: root/compiler/rustc_mir/src/transform/coverage/debug.rs
diff options
context:
space:
mode:
authorCamelid <camelidcamel@gmail.com>2021-03-01 16:33:47 -0800
committerCamelid <camelidcamel@gmail.com>2021-03-01 18:10:30 -0800
commit59ee8725482b98efdef08c40185462e7fa148c4a (patch)
treeb0c4d249f3002e1bb4019b6639ef3a7ad5697f48 /compiler/rustc_mir/src/transform/coverage/debug.rs
parent94736c434ee154b30e2ec22ec112b79e3f6c5884 (diff)
downloadrust-59ee8725482b98efdef08c40185462e7fa148c4a.tar.gz
rust-59ee8725482b98efdef08c40185462e7fa148c4a.zip
meta: Notify Zulip for rustdoc nominated issues
The rustdoc team does not currently use the `I-nominated` label, unlike
the libs and compiler teams (and maybe others). One reason for this is
that the other teams discuss their nominated issues in meetings, while
rustdoc is an async-only team.

However, it might be helpful to start using the `I-nominated` label for
rustdoc. The team currently uses a `cc @rust-lang/rustdoc` ping as the
equivalent, but it's easier to track issues when they use `I-nominated`.
Also we'd be more consistent with the other teams' procedures.

Since rustdoc doesn't have meetings, I propose we instead use the
triagebot notify Zulip functionality to create a topic in `#rustdoc` on
Zulip and ping the team. So it would look a bit like the procedure for
WG-prioritization when an issue acquires the `I-prioritize` label.
Diffstat (limited to 'compiler/rustc_mir/src/transform/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions