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 those procedures are for compiler-specific ping groups, whereas this is a general ping group.
Implementation steps
Relevant context
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 those procedures are for compiler-specific ping groups, whereas this is a general ping group.
Implementation steps
File a tracking issue in the rust-lang/compiler-team repository to collect your progress.Not compiler-specific ping group.relnotes-interest-groupping group team#1613relnotes-interest-groupping group #135032relnotes-interest-groupping group for release blog post blog.rust-lang.org#1453Create a PR for the rustc-dev-guide amending the notification group section to mention your group.T-release mostly, not compiler.relnotes-interest-groupping group team#1613.relnotes-interest-groupfor relnotes PRs and relnotes blog posts rust-forge#799Create 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.relnotes-interest-groupping group blog.rust-lang.org#1484, live at https://blog.rust-lang.org/inside-rust/2025/02/27/relnotes-interest-group.html.Relevant context