Request to create component for Tricium |
||
Issue descriptionCurrently issues related to Tricium (go/tricium) are filed under Infra>CodeAnalysis with label "Tricium", but this isn't very easily guessable since it doesn't include the project codename. I'd like to organize the Tricium bugs under a new component that's more guessable, like: Infra>Tricium Infra>Platform>Tricium Infra>CodeAnalysis>Tricium Which one of these seems the most appropriate?
,
Jun 1 2018
Possible ideas about what else would go in CodeAnalysis: - Anything related to linters run anywhere - Things related to specific Tricium Analyzers Current bugs in Infra>CodeAnalysis without label:Tricium: https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3AInfra%3ECodeAnalysis+-label%3Atricium This appears to include things related to git cl lint and clang. Note, Tools>CodeCoverage is a separate component. Infra>SDK would cover git-cl and presubmit support itself. How about Infra>Platform>Tricium for bugs about Tricium (because other chops-developed platforms meant to be used by multiple teams are under Infra>Platform), and possibly either Infra>CodeAnalysis or Infra>Platform>Tricium>Analyzers for bugs about common (non-project-specific) analyzers?
,
Jun 1 2018
Infra>Platform>Tricium also sgtm.
,
Jun 15 2018
I'll do Infra>Platform>Tricium. Feel free to move all of the bugs over (or let me know which filter to use to migrate and I can help). We can talk about Infra>Platform>Tricium>Analyzers later?
,
Jun 15 2018
Created. |
||
►
Sign in to add a comment |
||
Comment 1 by benhenry@google.com
, Jun 1 2018