New issue
Advanced search Search tips

Issue 642755 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

WebRTC Bugdroid not working?

Project Member Reported by kjellander@chromium.org, Aug 31 2016

Issue description

There are several cases where the WebRTC bugdroid no longer posts to Chromium bugs:

https://bugs.chromium.org/p/chromium/issues/detail?id=634266
should have gotten posts from 
https://codereview.webrtc.org/2292233003/
https://codereview.webrtc.org/2293203003/

Is this related to the newly updated Bugdroid?
In the old bugdroid, it had an implicit assumption on a bug being a Chromium bugs when no prefix was used (e.g. BUG=XXXXXX), so the team has learned to prefix all WebRTC bugs with BUG=webrtc:XXXX

Could that have changed now? Do we need to prefix Chromium bugs as well now?
 
Cc: -tandrii@chromium.org aga...@chromium.org
Components: -Infra Infra>Platform
Labels: Infra-Troopers
agable@ is new owner of bugdroid.

Comment 2 by estaab@chromium.org, Aug 31 2016

Owner: aga...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to agable@ directly for possible answers.

Comment 3 by aga...@chromium.org, Aug 31 2016

Status: WontFix (was: Assigned)
This has been true since March 2014: https://chromereviews.googleplex.com/30177014

Ever since then, webrtc has always been the 'default' project, with chromium requiring a prefix.

We could change it back, but it's been this way for over two years now, so I doubt that would be a good idea.

Here's an example of people using chromium:NNN https://codereview.webrtc.org/2299643002/
And here's an example of people using just numbers for webrtc: https://codereview.webrtc.org/2273473002
Oh dear, it's been fixed for two years? Too bad I wasn't CCed on that CL.

I'll send out a clarification to the team. I guess we're not using BUG=XXXX to reference Chromium that often.

Sign in to add a comment