@WG-prioritization/alerts issue #82437 has been requested for prioritization.
Current beta and nightly channels don't experience this issue
This is fixed now it seems
Would that deserve a stable backport?
I think we should nominate it for a meeting, but this doesn't really fall under T-prioritization IMO
Right, nomination sounds correct to me
No one nominated; should I nominate for
estebank marked this as
T-compiler, but since it's fixed I don't think that's right.
Issue #82437's prioritization request has been removed.
T-release, nominated, and removed
cc @Esteban Küber - I'd be interested to hear why you marked it as T-compiler
Ah didn't catch it was fixed in beta
That's why I assumed it required someone from the team to triage and I monitor that tag frequently.
^^ @Joshua Nelson
I'll comment on the issue that it's fixed on beta
oh Camelid already did
who should be the recipient for the
I-nominate label? The compiler or the release team? If the latter how do they catch this issue for discussion?
cc @Camelid + @Joshua Nelson
also cc @DPC (release team)
stable-nominate the PR that fixed the issue (or is there none?)
I don't think we know what PR caused the issue. I've marked it now as