Stream: t-compiler/wg-prioritization/alerts

Topic: I-prioritize #74539 ICE with the `@ ..` binding pattern


triagebot (Jul 19 2020 at 23:55, on Zulip):

@WG-prioritization/alerts issue #74539 has been requested for prioritization.

Procedure

Yuki Okushi (Jul 20 2020 at 13:25, on Zulip):

it's caused by #72677 so stable-to-stable regression

Yuki Okushi (Jul 20 2020 at 13:48, on Zulip):

the fix is up, r+'d, and nominated for stable & beta backports

Yuki Okushi (Jul 21 2020 at 06:56, on Zulip):

the fix lands on master, I still keep this issue open to track backports

Yuki Okushi (Jul 21 2020 at 06:59, on Zulip):

so, we could remove I-prioritize in such a case, or should label P-medium or so?

LeSeulArtichaut (Jul 21 2020 at 10:16, on Zulip):

I think we can just remove I-prioritize since the attention will be focused on the PR rather then on the issue itself

DPC (Jul 21 2020 at 10:23, on Zulip):

i was wondering if we should create a separate issue for the backport and prioritise that instead

LeSeulArtichaut (Jul 21 2020 at 11:25, on Zulip):

Or maybe we could have status labels for issues that can reflect that the issue is waiting for backport

DPC (Jul 21 2020 at 11:48, on Zulip):

well the thing is prs often mention something as closes #issue-number

triagebot (Jul 21 2020 at 13:20, on Zulip):

Issue #74539's prioritization request has been removed.

Yuki Okushi (Jul 21 2020 at 13:25, on Zulip):

removed I-prioritize label, I like LeSeulArtichaut 's idea, it'd be useful to avoid confusion

Santiago Pastorino (Jul 22 2020 at 15:28, on Zulip):

in general I think if it's not too much of a hassle I'd prioritize even issues that have a pending PR

Santiago Pastorino (Jul 22 2020 at 15:28, on Zulip):

because that's a nice input when beta/stable nominations are discussed

Santiago Pastorino (Jul 22 2020 at 15:29, on Zulip):

this nomination is about a P-low issue or is it about a P-critical one?

Last update: Apr 15 2021 at 02:15UTC