New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 805637 link

Starred by 1 user
Status: Fixed
Owner:
efoo@chromium.org
Closed: Jan 2018
Cc:
llozano@chromium.org
█ laszio@chromium.org
█ yunlian@chromium.org
abodenha@chromium.org
vapier@chromium.org
█ benhenry@chromium.org
█ rahulchaudhry@chromium.org
ovanieva@chromium.org
manojgupta@chromium.org
cmt...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

[Component Request] "Infra>Platform>Chromeos-Toolchain"

Project Member Reported by cmt...@chromium.org, Jan 24 2018 
1] Component Name: Chromeos-Toolchain



2] Parent Component (e.g. Blink, UI>Browser, etc...): Infra>Platform


3] Description of Component: Issues relating to Chrome OS toolchain (compiler, linker, debugger, system libraries, etc.)

4] Admin/ Owner: llozano@

5] Please specify what triage practices will be followed for the component
(i.e. what team will do it and how frequently).

The ChromeOS Toolchain team monitors incoming bugs continually. P0's are triaged immediately; P1's are triaged within 24 hours.  Others are triaged as soon as possible.

Comment 1 by cmt...@chromium.org, Jan 24 2018

Cc: manojgupta@chromium.org yunlian@chromium.org cmt...@chromium.org laszio@chromium.org rahulchaudhry@chromium.org llozano@chromium.org

Comment 2 by cmt...@chromium.org, Jan 25 2018

Components: -Infra Admin>ComponentRequest

Comment 3 by cmt...@chromium.org, Jan 25 2018 

Ping?

Comment 4 by cmt...@chromium.org, Jan 26 2018

Cc: ovanieva@chromium.org abodenha@chromium.org
Ping? Ping?  Is anybody working on this?

Comment 5 by cmt...@chromium.org, Jan 26 2018

Cc: benhenry@chromium.org

Comment 6 by efoo@chromium.org, Jan 27 2018

Owner: efoo@chromium.org
Status: Assigned (was: Untriaged)
Assigned to efoo@

Infra>Platform is not the right location for this since Infra>Platform mainly serves the Chrome Ops Foundation team

IMO, this should be under OS>Toolchain. Please confirm.

Comment 7 by cmt...@chromium.org, Jan 28 2018 

We really need "ChromeOS" somewhere in the Component name, as we do not want (and do not handle) Toolchain bugs for Linux, Windows, or MacOS.

Comment 8 by cmt...@chromium.org, Jan 28 2018 

*Maybe*  "OS>Chromeos-Toolchain"  Or "Tools>Chromeos-Toolchain" ?

Comment 9 by llozano@chromium.org, Jan 29 2018

Cc: akes...@chromium.org vapier@chromium.org
my preference is for Tools>ChromeOS-Toolchain.
If anyone is going to object please do so by Monday noon Pacific.

Comment 10 by cmt...@chromium.org, Jan 30 2018 

No objections have been raised to "Tools>ChromeOS-Toolchain", so please create that component for us.

Comment 11 by efoo@chromium.org, Jan 31 2018

Status: Fixed (was: Assigned)
Created.

Comment 12 by llozano@chromium.org, Jan 31 2018 

Thanks. Is there a way to programmatically add this component for everything with label:build-toolchain?

Comment 13 by llozano@chromium.org, Feb 5 2018 

ping?

Comment 14 by cmt...@chromium.org, Feb 5 2018 

It can be done pretty easily manually: select all the bugs with label:build-toolchain, choose 'bulk edit' from the actions menu, and add the new component.  I've done this for our build-toolchain issues now.

Comment 15 by akes...@chromium.org, Feb 5 2018

Cc: -akes...@chromium.org

Comment 16 by efoo@chromium.org, Feb 9 2018 

FYI, added rule where component=Tools>ChromeOS-Toolchain, then build-toolchain label is assigned to the bug.
►

Sign in to add a comment