Configure bootstrap backport nominations through triagebot by jieyouxu · Pull Request #141967 · rust-lang/rust (original) (raw)

Following the discussion in #t-infra/bootstrap > ✔ Have triagebot create backport nomination threads? where we noticed that bootstrap backport nominations were difficult to track, since:

• We don't really have a dedicated person / group of people checking for bootstrap backport nominations.
• We don't really have an establish way of handling bootstrap backports.

This PR configures triagebot to open backport nominations threads (indicated for bootstrap team if a given PR has the suitable team label, T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)) in #t-infra/bootstrap/backports. The current configuration is such that the whole bootstrap team will be pinged for bootstrap backport nominations1.

Steps

• Ping members who opt-in subscribe to backport channel, or ping the whole bootstrap team?
  • Poll: #t-infra/bootstrap > Have triagebot create backport nomination threads? @ 💬
  • Votes (as of 2025-06-10): 3 votes "no preference", 1 vote "in favor".
• (Best for follow-up) Maybe also document bootstrap team's backport process / decision process in Forge? It's a bit different from compiler team's backport process because we don't have weekly bootstrap triage meetings and thus don't have sync backport decisions.
  • Tracked as follow-up in Forge: Document bootstrap team's backport process rust-forge#889.

r? Kobzol

Footnotes

1. Note that this configuration is similar to the types team backport nominations, but diverges from the compiler team. ↩