-
Notifications
You must be signed in to change notification settings - Fork 13.8k
Disable triagebot auto stable-regression compiler backport nominations pending redesign #147263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable triagebot auto stable-regression compiler backport nominations pending redesign #147263
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok with disabling both stable and beta auto-nominations but I understood from that thread that stable auto-nominations were too eager
No prejudice against re-enabling them if the nominations include a bit more context on _why_ it's automatically nominated and _which_ regression(s) are being addressed. Or as proposed, it could also simply become a reminder-to-nominate _comment_.
f7f9846
to
16cfde9
Compare
Modified to only disable the stable auto backport nominations, since stable backports have a substantially higher bar, which makes those very prone to false positives. |
(Also this is r-l/r so you'll need to bors 😁) |
@bors r=apiraino,Urgau |
@bors rollup |
Rollup of 6 pull requests Successful merges: - #141839 (make rust-analyzer use a dedicated build directory) - #146166 (Implement range support in `//@ edition`) - #147259 (cg_llvm: Use helper methods for all calls to `LLVMMDNodeInContext2`) - #147263 (Disable triagebot auto stable-regression compiler backport nominations pending redesign) - #147268 (add arm-maintainers to various targets) - #147270 (Move doc_cfg-specific code into `cfg.rs`) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of #147263 - jieyouxu:disable-auto-backport-nominations, r=apiraino,Urgau Disable triagebot auto stable-regression compiler backport nominations pending redesign Current auto compiler stable-regression backport nominations seem to be too aggressive, and seems to unfortunately lower signal-to-noise ratio of the compiler backport channel. So this PR disables the triagebot compiler auto stable-regression backport nominations pending a redesign. Beta-regression auto backport nominations are not modified, we might want to gather some more experience with it. No prejudice against re-enabling them if the nominations include a bit more context on _why_ it's automatically nominated and _which_ regression(s) are being addressed. Or as proposed, it could also simply become a reminder-to-nominate _comment_. cf. [#t-compiler/backports > #146919: stable-nominated @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/474880-t-compiler.2Fbackports/topic/.23146919.3A.20stable-nominated/near/540979327) > I like the idea of rustbot just posting a message that suggests adding the label. That seems like a good compromise between avoiding forgotten nominations and avoiding spurious nominations. In any case, this was very much worth experimenting! r? `@apiraino` (or triagebot)
Current auto compiler stable-regression backport nominations seem to be too aggressive, and seems to unfortunately lower signal-to-noise ratio of the compiler backport channel. So this PR disables the triagebot compiler auto stable-regression backport nominations pending a redesign. Beta-regression auto backport nominations are not modified, we might want to gather some more experience with it.
No prejudice against re-enabling them if the nominations include a bit more context on why it's automatically nominated and which regression(s) are being addressed. Or as proposed, it could also simply become a reminder-to-nominate comment.
cf. #t-compiler/backports > #146919: stable-nominated @ 💬
In any case, this was very much worth experimenting!
r? @apiraino (or triagebot)