5 ms·

Does this mean Chromium is also moving away from Google Code? I'm curious how Google plans to migrate almost 500,000 bug reports. I'm expecting Google to purch

by pdknsk 12y ago

Does this mean Chromium is also moving away from Google Code? I'm curious how Google plans to migrate almost 500,000 bug reports. I'm expecting Google to purchase GitHub next in order to improve its deficiencies. In particular code search, which is really poor. Google Code search is good, so Google can then apply its search expertise "in-house". https://code.google.com/p/chromium/codesearch https://code.google.com/p/chromium/codesearch Maybe it's just habitual, but I prefer the issue tracker on Google Code as well.

jefftchan 12y ago
Chromium is already on Github. https://github.com/chromium https://github.com/chromium
daw___ 12y ago
I guess they will be using their own tool to migrate issues: IssueExporterTool "How to export Google Code issue tracker data to other services" https://code.google.com/p/support-tools/wiki/IssueExporterTool https://code.google.com/p/support-tools/wiki/IssueExporterTo...
- mike_hearn 12y ago
  The problem is that last time I looked at these tools, they all sucked. I migrated code hosting and website for my project to github but left issue tracking on Google Code because the github API doesn't let you do any kind of high fidelity import of issues. I hope GH find a way to do some kind of reasonable issue import soon.
  - scrollaway 12y ago
    The API doesn't, but if you contact the Github team, they have ways of doing much higher fidelity bug imports if you give them massaged data. Here is an example of a project we imported from Bugzilla: https://github.com/translate/pootle/issues?page=47&q=is%3Aissue+is%3Aclosed https://github.com/translate/pootle/issues?page=47&q=is%3Ais... (all issues below id ~3200 are imported). Here is the tool I wrote for the occasion: https://github.com/jleclanche/bugzilla-to-github/ https://github.com/jleclanche/bugzilla-to-github/
lnanek2 12y ago
At least for Android bug reports, Google mostly ignores them and closes them all as obsolete every release even though they weren't fixed. So I don't think they'll have any problem ditching Chromium bug reports. I've heard they have an internal bug tracker anyway, so the public ones like b.android.com are just jokes on people who don't know any better.
- notatoad 12y ago
  no, they mostly don't do that. you just think they do because you only hear about it when the internet gets angry about something. The chromium bugtracker is very active and the chromium developers are very open and helpful on it.
durin42 12y ago
Chromium is already on googlesource.com, which is a different service. They have a plan for issue tracking, but it's not yet ready for prime-time.
jscheel 12y ago
Last error report I created (which is consistently causing tab crashes) was marked as duplicate and merged (without comment) into an issue that is private and inaccessible. All attempts to get additional information have been met with silence.
- magicalist 12y ago
  That sounds like it means it's a security issue. All the browsers do this (the ones with open issue trackers, at least)
  - jscheel 12y ago
    Ah, good point. That could very well be it. Of course, the last issue I found was a security hole in google's core data api. Their review team admitted it was an issue, but rejected fixing it or rewarding a bounty, because they decided it was too esoteric. Even though it is literally a huge api key check that just doesn't happen. I've had bad experiences with filing bug reports to google :)
pbhjpbhj 12y ago
>I'm expecting Google to purchase GitHub next // So basically this is our 5 year warning on GitHub closing down !?

by pdknsk 12y ago

jefftchan 12y ago

Chromium is already on Github. https://github.com/chromium https://github.com/chromium

daw___ 12y ago

I guess they will be using their own tool to migrate issues: IssueExporterTool "How to export Google Code issue tracker data to other services" https://code.google.com/p/support-tools/wiki/IssueExporterTool https://code.google.com/p/support-tools/wiki/IssueExporterTo...

mike_hearn 12y ago
The problem is that last time I looked at these tools, they all sucked. I migrated code hosting and website for my project to github but left issue tracking on Google Code because the github API doesn't let you do any kind of high fidelity import of issues. I hope GH find a way to do some kind of reasonable issue import soon.
- scrollaway 12y ago
  The API doesn't, but if you contact the Github team, they have ways of doing much higher fidelity bug imports if you give them massaged data. Here is an example of a project we imported from Bugzilla: https://github.com/translate/pootle/issues?page=47&q=is%3Aissue+is%3Aclosed https://github.com/translate/pootle/issues?page=47&q=is%3Ais... (all issues below id ~3200 are imported). Here is the tool I wrote for the occasion: https://github.com/jleclanche/bugzilla-to-github/ https://github.com/jleclanche/bugzilla-to-github/

lnanek2 12y ago

At least for Android bug reports, Google mostly ignores them and closes them all as obsolete every release even though they weren't fixed. So I don't think they'll have any problem ditching Chromium bug reports. I've heard they have an internal bug tracker anyway, so the public ones like b.android.com are just jokes on people who don't know any better.

notatoad 12y ago
no, they mostly don't do that. you just think they do because you only hear about it when the internet gets angry about something. The chromium bugtracker is very active and the chromium developers are very open and helpful on it.

durin42 12y ago

Chromium is already on googlesource.com, which is a different service. They have a plan for issue tracking, but it's not yet ready for prime-time.

jscheel 12y ago

Last error report I created (which is consistently causing tab crashes) was marked as duplicate and merged (without comment) into an issue that is private and inaccessible. All attempts to get additional information have been met with silence.

magicalist 12y ago
That sounds like it means it's a security issue. All the browsers do this (the ones with open issue trackers, at least)
- jscheel 12y ago
  Ah, good point. That could very well be it. Of course, the last issue I found was a security hole in google's core data api. Their review team admitted it was an issue, but rejected fixing it or rewarding a bounty, because they decided it was too esoteric. Even though it is literally a huge api key check that just doesn't happen. I've had bad experiences with filing bug reports to google :)

pbhjpbhj 12y ago

>I'm expecting Google to purchase GitHub next // So basically this is our 5 year warning on GitHub closing down !?