Google has too long a history of stonewalling and foot dragging. You NEED that kind of 'motivation' -- unless you finally learn to take responsibility for committing to fix your bugs without such unpleasant prodding.
When, for example, are you going to fix AAC+ support in StageFright? When will you fix 5211? It has been open since Dec 4, 2009! And what about 2207? It has been open for longer, since March 2009. And it is much more serious. You are losing customers because of this bug, yet you do nothing. Finally, would you consider the previous poster's proposal of "running for the hills" more motivating? Which would you rather have? Developers abandoning the Android platform because of the poor prognosis for Proguard, or developers who stick with the platform but loudly call for badly needed change? On Sep 23, 9:34 pm, Dianne Hackborn <[email protected]> wrote: > On Thu, Sep 23, 2010 at 6:50 PM, Indicator Veritatis <[email protected]>wrote: > > > But rather than run for the hills, we should pepper Google with > > uncomplimentary speculations concerning their motives for this "turd > > layering" until they 'fess up and give us a release date for a version > > of ADT that will allow us to include Proguard in an Eclipse build > > WITHOUT these problems. > > You sure know how to motivate people. > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
