Speed>Tracing component is unmonitored |
||||
Issue descriptionCould we remove the Speed>Tracing component? As I found out in issue 702645 , the proper channel for tracing viewer bugs is https://github.com/catapult-project/catapult/issues. Having an unmonitored Speed>Tracing component is misleading. A quick search shows a number of bugs filed in the last month that aren't getting triaged: https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3ASpeed%3ETracing++opened%3Etoday-30&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids
,
Apr 28 2017
Annie - what do we want to do? Is it time to reel in github bugs, or should we remove the component?
,
May 8 2017
I'm not sure. I think the bigger problem is ownership: there isn't a process for triaging tracing bugs that don't block telemetry, metrics, etc.
,
Dec 8 2017
Annie - let's talk about this when it's on the top of your list.
,
Jul 10
|
||||
►
Sign in to add a comment |
||||
Comment 1 by sullivan@chromium.org
, Apr 28 2017