Re: How to do issue triage in web-platform-tests?

I've added the labels now, and
https://github.com/w3c/web-platform-tests/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Ainfra%20-label%3Apriority%3Abacklog%20-label%3Apriority%3Aroadmap%20-label%3Apriority%3Aurgent
is
a link one might use to do triage of the infra label.

On Thu, Sep 14, 2017 at 8:35 AM Philip Jägenstedt <foolip@google.com> wrote:

> On Thu, Sep 14, 2017 at 8:14 AM James Graham <james@hoppipolla.co.uk>
> wrote:
>
>> On 14/09/17 12:57, Bob Holt wrote:
>> > Re: labels, and building on James's suggestions I propose:
>> > - priority:urgent
>> > - priority:roadmap
>> > - priority:backlog
>>
>> That seems reasonable to me. Agreed that prioritisation is hard without
>> some way to ensure that people actually work on the prioritized things,
>> but hopefully we have enough regular contributors — including people who
>> are paid to work on this — and good enough cooperation to make it happen.
>>
>
> This all sounds good to me, and not doing anything with milestones at this
> point simplifies things. I expect that for most issues with
> priority:roadmap, they'll be tracked by some external process, like Google
> OKRs and similar.
>
> I'd like to add these labels and go ahead to start with a triage of all
> infra issues, as part of the ecosystem infra rotation
> <https://docs.google.com/document/d/10och6DoxEe6AhQX7MiQR8AhtjDheKIlf-GpF0impeJQ/edit?usp=sharing>
> .
>
> If there are no concerns in 24 hours, let's do it!
>