@WG-prioritization/alerts issue #77653 has been requested for prioritization.
I-nominated?So anyone can use rustbot to add regression labels now? Sweet
Yeah, after a call in internal forum complaining about 1.46 release.
it's not clear to me if this issue was previously working and now ICEs or what
if that's the case this one need to be P-critical I'd say
cc @lzutao
also @lzutao mentioned someone complaining about 1.46 release and I guess sharing this issue, can you share the link?
More details in the linked issue #77638, thus I will assign the same P-critical, makes sense?
@Santiago Pastorino the linked 77638 issue has a couple of playground links to repro the issue. Would it be enough to remove the MCVE label from this issue?
Issue notifications now here
Santiago Pastorino said:
it's not clear to me if this issue was previously working and now ICEs or what
I'm not sure, but the original author said that
he tried porting their code to compile with latest nightly and he almost got it working.
So, I think the code was compiled before.
Santiago Pastorino said:
also lzutao mentioned someone complaining about 1.46 release and I guess sharing this issue, can you share the link?
https://internals.rust-lang.org/t/1-46-is-unusable-for-me-solved/13161
it is not related to this issue, but an infra member said they didn't receive see regression-from-stable-to-beta,
one complains that they couldn't tag it because they aren't org members.
@Camelid sent a PR to enable the label for rustbot which normal users can use.
someone mentioned making a blog post about that
anyone want to volunteer? :P
About this issue?
about allowing non-org members to mark issues about regressions
ah i see
I have no idea about bet regression triage process :sweat_smile:
Working on a blog post.