diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-06-11 13:48:08 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-11 13:48:08 +0200 |
| commit | 471dee2ca82da247e314a66bd3d0e89bb1fec5ed (patch) | |
| tree | 64713044bfecf8160275be91d7ebc0a5490d182f /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 0a39445252ac076ef573bcacee63bbdc59497b52 (diff) | |
| parent | 6f487586f86a28982242dfb5ee660170c1a0f2d5 (diff) | |
| download | rust-471dee2ca82da247e314a66bd3d0e89bb1fec5ed.tar.gz rust-471dee2ca82da247e314a66bd3d0e89bb1fec5ed.zip | |
Rollup merge of #141967 - jieyouxu:bootstrap-backports, r=Kobzol
Configure bootstrap backport nominations through triagebot
Following the discussion in [#t-infra/bootstrap > ✔ Have triagebot create backport nomination threads?](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/.E2.9C.94.20Have.20triagebot.20create.20backport.20nomination.20threads.3F/with/521876500) 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, https://github.com/rust-lang/rust/labels/T-bootstrap) in [#t-infra/bootstrap/backports](https://rust-lang.zulipchat.com/#narrow/channel/507486-t-infra.2Fbootstrap.2Fbackports). The current configuration is such that **the whole bootstrap team will be pinged for bootstrap backport nominations**[^diverges].
### Steps
- [x] ~~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? @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/Have.20triagebot.20create.20backport.20nomination.20threads.3F/near/522141337)
- Votes (as of 2025-06-10): 3 votes "no preference", 1 vote "in favor".
- [x] ~~(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](https://forge.rust-lang.org/compiler/backports.html) because we don't have weekly bootstrap triage meetings and thus don't have sync backport decisions.~~
- Tracked as follow-up in Forge: https://github.com/rust-lang/rust-forge/issues/889.
---
r? Kobzol
[^diverges]: Note that this configuration is similar to the types team backport nominations, but diverges from the compiler team.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions