What to do with former Blink>Internals bugs

[David Bokan]

I vaguely remember seeing an e-mail go by about the deprecation of Blink>Internals but I can't for the life of me find it now.

What bucket should we put refactoring type bugs (particularly ones that aren't obviously related to any one component) that previously would have belonged to Blink>Internals? The global Internals? Somewhere else?

Thanks,
David

[TAMURA, Kent]

I haven't seen any announcement about Blink>Internals deprecation.

haraken@, do you know who is responsible for Blink>Internals deprecation?

Anyway, if we can't use Blink>Internals, how about using component=Blink and Type=Task?

--
You received this message because you are subscribed to the Google Groups "Component:Blink bug rotation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crblink-rotati...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/crblink-rotation/CANMmsAvSagr3D%3DEXSAsRk6dg%3Dac9PvMBAzqbitF-dMFv6qZZmg%40mail.gmail.com.

--

TAMURA Kent
Software Engineer, Google

[Kentaro Hara]

haraken@, do you know who is responsible for Blink>Internals deprecation?

+Johann Koenig is working on it. Here's a guideline doc.

The problem is that people are using Blink>Internals as a "catch-all" label and there is no owner team. The idea is to classify existing bugs to more proper labels (in common cases, they should go to Blink>Internals>XXX) and deprecate it.

--

Kentaro Hara, Tokyo

[Johann Koenig]

On Fri, Oct 2, 2020 at 3:53 PM Kentaro Hara <har...@chromium.org> wrote:

haraken@, do you know who is responsible for Blink>Internals deprecation?

+Johann Koenig is working on it. Here's a guideline doc.

The discussion was first brought up here: https://groups.google.com/a/google.com/g/chrome-architecture-tok/c/RFd44B_L3kw/m/4KPZK-iRAAAJ

 

The problem is that people are using Blink>Internals as a "catch-all" label and there is no owner team. The idea is to classify existing bugs to more proper labels (in common cases, they should go to Blink>Internals>XXX) and deprecate it.

On Fri, Oct 2, 2020 at 11:18 AM TAMURA, Kent <tk...@chromium.org> wrote:

I haven't seen any announcement about Blink>Internals deprecation.

haraken@, do you know who is responsible for Blink>Internals deprecation?

Anyway, if we can't use Blink>Internals, how about using component=Blink and Type=Task?

On Thu, Sep 24, 2020 at 11:39 AM 'David Bokan' via Component:Blink bug rotation <crblink-...@chromium.org> wrote:

I vaguely remember seeing an e-mail go by about the deprecation of Blink>Internals but I can't for the life of me find it now.

What bucket should we put refactoring type bugs (particularly ones that aren't obviously related to any one component) that previously would have belonged to Blink>Internals? The global Internals? Somewhere else?

It depends on what is being refactored. Which issue are you trying to triage? 

[David Bokan]

Thanks all for the pointers. Didn't know the sub categories under Blink>Internals are still ok.

It depends on what is being refactored. Which issue are you trying to triage? 

There were a couple last week when I was on my shift last week but I can't find them now. The only one I remember was 639244, which was simply closed. If it hadn't would that belong under Blink>Internals>Frames, since I guess you could argue it's embedder related? In general, cross-cutting refactorings (e.g. replace uses of Type) don't seem like they have a home. Should they just go to the team/project that proposed them?