Stream: t-release/triage

Topic: questions about triaging issues.


view this post on Zulip Charles Lew (Jun 11 2020 at 01:22):

@DPC Could you say a little more about what exactly do we need to do about triaging issues? I haven't been triaging issues, but i figured maybe i could start doing so. I've read the forge docs and it gives a filter, but there're 800+ issues in it.

view this post on Zulip DPC (Jun 11 2020 at 01:23):

Well uhm you need to triage new issues not the older ones. So just the ones that are not labelled or more labels could be added to (focus on the newer ones)

view this post on Zulip Charles Lew (Jun 11 2020 at 01:24):

OK, that's fine, but is it the intention that we clear up this filter bit by bit?

view this post on Zulip Charles Lew (Jun 11 2020 at 01:24):

Or just leave the old issues alone.

view this post on Zulip Charles Lew (Jun 11 2020 at 01:28):

Besides this, i've read some of the issues, and find that our C-* tags a little lacking and doesn't cover a few cases.

view this post on Zulip DPC (Jun 11 2020 at 01:32):

You are free to triage them if you wish

view this post on Zulip Charles Lew (Jun 11 2020 at 01:33):

Let me list a few examples:

view this post on Zulip Charles Lew (Jun 11 2020 at 01:53):

view this post on Zulip Owen Salter (Jun 11 2020 at 02:11):

should we be triaging issues as well as PRs?

view this post on Zulip DPC (Jun 11 2020 at 10:27):

@Owen Salter it's what the group does in general but we don't hold everyone to it. Since you are new, I'd say you can focus on PRs first till you are familiar with the process :slight_smile:

view this post on Zulip Owen Salter (Jun 11 2020 at 12:15):

gotcha, i'm looking forward to helping out!

view this post on Zulip Léo Lanteri Thauvin (Jun 11 2020 at 15:03):

@Charles Lew (and also @Owen Salter if you want)
Here are some things I think I can tell you about triaging compiler bugs, as a member of the Prioritization WG:

The most important labels to add IMO are:

If you think the bug deserves some attention, don't hesitate, please tag it as I-prioritize. This will ping the Prioritization WG so we can discuss the priority of the given bug, nominate it to T-compiler meetings, etc. Note that regressions (and soon soundness issues) are automatically prioritized.

Also don't forget to add the C-bug and T-compiler. Because it looks better :D

cc @Santiago Pastorino what do you think about all this :point_up:? Do you have anything to correct/add?

view this post on Zulip Santiago Pastorino (Jun 11 2020 at 15:04):

it's very important to add T labels, T-compiler, T-lang, T-libs, T-rustdoc for instance and also libs-impl when a problem is about stdlib but it's about the implementation and not a design decision

view this post on Zulip Santiago Pastorino (Jun 11 2020 at 15:05):

I think what @LeSeulArtichaut has said is great, also, why don't we document this on forge? if we had not done it yet :)

view this post on Zulip Léo Lanteri Thauvin (Jun 11 2020 at 15:08):

I think there already is some documentation on the forge

view this post on Zulip Léo Lanteri Thauvin (Jun 11 2020 at 15:08):

But as things moved a lot for compiler bugs...

view this post on Zulip Charles Lew (Jun 11 2020 at 17:06):

Thanks~

view this post on Zulip Léo Lanteri Thauvin (Jun 11 2020 at 17:11):

You're welcome :upside_down:


Last updated: Jan 26 2022 at 14:20 UTC