Tracking Issue for relnotes interest group ping group

[jieyouxu]

Tracking issue for creating a ping group for relnotes PRs so interested contributors can get pinged for that specific purpose (instead of pinging whole teams like T-compiler which has idk 50+ members). Note that the following steps are derived from T-compiler notification group procedure but adjusted because it's compiler-specific ping groups.

Implementation steps

• File a tracking issue in the rust-lang/compiler-team repository to collect your progress. Not compiler-specific ping group.
• Create a PR against the rust-lang/team repository adding the notification group. Create relnotes-interest-group ping group team#1613
• Configure the rust-lang/rust repository to accept triagebot commands for this group. triagebot: register relnotes-interest-group ping group #135032
• Create a PR for the rustc-dev-guide amending the notification group section to mention your group. T-release mostly, not compiler.
• Create a sample PR for the rust-lang/team repository showing how one can add oneself. This will be referenced by your blog post to show people how to join. See Create relnotes-interest-group ping group team#1613.
• Create a PR for the forge release notes section to describe the relnotes interest group ping group.
• Create a Zulip stream for the notification group. If you don’t have the permission to do, you can ask on #t-compiler/wg-meta. Unclear if needed, probably better to discuss on the relnotes PR itself.
• Write an announcement blog post for Inside Rust and open a PR against blog.rust-lang.org.

Relevant context

• Zulip discussion: https://rust-lang.zulipchat.com/#narrow/channel/241545-t-release/topic/Please.20CC.20lang