| 1 |
On Wed, Sep 02, 2015 at 09:17:16PM +0200, Paweł Hajdan, Jr. wrote: |
| 2 |
> On 8/30/15 12:02 PM, Kent Fredric wrote: |
| 3 |
> > Or upstream might be a monolithic giant like Google where their |
| 4 |
> > upstream bug tracking is some pointless forum where you get ignored by |
| 5 |
> > the people actually working on things. |
| 6 |
> |
| 7 |
> Ouch. |
| 8 |
> |
| 9 |
> Do you have specific examples? |
| 10 |
> |
| 11 |
> I'm not denying they exist. I just had mostly positive experience with |
| 12 |
> <https://code.google.com/p/chromium/issues> . Because I'm also Chromium |
| 13 |
> developer, I know that's what people "actually working on things" use. |
| 14 |
> |
| 15 |
> I admit with 85000+ open issues not all of them are getting enough |
| 16 |
> attention. But if you know an upstream developer, it's easier to get the |
| 17 |
> right people to look at the bug. |
| 18 |
> |
| 19 |
> Of course above is not the only Google project, and I don't have much |
| 20 |
> experience with the other ones. |
| 21 |
> |
| 22 |
> Paweł |
| 23 |
|
| 24 |
I dont know what ones he's talking about, but I have this one: |
| 25 |
|
| 26 |
https://code.google.com/p/android/issues/detail?id=175284 |
| 27 |
https://bugs.gentoo.org/show_bug.cgi?id=533178 |
| 28 |
|
| 29 |
Android Studio is released as a compiled binary for windows/mac/linux |
| 30 |
but there is no source code for it. And to make matters even worse they |
| 31 |
don't have proper tags in the git repos for it so I can't even just make |
| 32 |
the tarballs myself because I dont know which commits correspond to the |
| 33 |
releases. They just closed the bug as declined with no reason given :(. |
| 34 |
|
| 35 |
-- Jason |
Archives