Hi All, Thanks for the feedback.
Mark, I'd LOVE to come to I|O but unfortunately i'm in Australia and can't justify the expense! Many Android devs aren't based in the USA ;-) Also, in regards to competitor's public bug trackers, they all require a developer login, but these aren't hard to get. Apple: https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/wa/signIn Microsoft: http://wp7guide.codeplex.com/workitem/list/basic Blackberry: http://us.blackberry.com/developers/resources/issuetracker/ I've heard on the grapevine that MS and BB are actually quite responsive. Apparently Apple aren't. Having never dealt with any of them I can't say for sure. Tim, unfortunately there are already a couple of issues with more than 5000 stars that have been open since late 2009 and still have the status "New". Should we try for 50000 stars? Chris, thanks for pointing out that the Android devs DO occasionally respond, but the example you cited was fairly obviously not a Google issue (unless they wanted to roll MoonLight into WebKit which doesn't seem likely). What about the issues that can only be solved by an official patch to the Android source? (No rooting, no custom ROMS etc.) Mike. On Mar 16, 3:35 am, Tim Mensch <[email protected]> wrote: > On 3/15/2011 9:30 AM, Chris Becker wrote: > > > It seems reasonable that the most effective way to get a response > > would be to rally the troops and have excessive confirms and > > comments on the specific issue/bug. If 500 stars/comments doesn't do > > it, maybe 5000 will. At the very least, there seems no harm in doing > > so... Is this the right issue: > > <http://code.google.com/p/android/issues/detail?id=3434> > > Yes, that's the low-latency issue that I know about, at least. I've had > it starred for a long time myself, and even provided a detailed comment > (#53) plus a couple of other responses. > > Please star the issue if it's important to you, though given that issue > is coming up on two years old, and is still "Status: New", with the only > interactions from Google being to categorize it as "Component-GfxMedia", > I do have my doubts that the issue tracker gives an issue much weight. > They did add the "low-latency" flag, even if they didn't make it low > enough latency to be useful, though, so maybe I'm wrong. > > Tim -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
