Hi, unfortunately there is no way for this to happen. There are a number of things at play:
- Only critical bugs (typically meaning security bugs) are at all likely to warrant delivering an update. There is a lot of work around building (for the rapidly growing number of device configurations), qualifying, carrier accepting, and delivering such updates. - We are still dealing with accepting external contributions into the code. I think this will start happening significantly in Eclair, but at this point very few have made it in. - We actually wouldn't want this kind of bug fix in an intermediate release, since it impacts the behavior of applications. This kind of change would require bumping the platform SDK version so that applications can indicate that they only work with a newer version that has the change, and we would like to only make such a change in more significant platform releases to help control the number of such versions that developers must deal with. - Increasingly, there is just not going to be a way to push all devices up to newer versions, so dealing with older versions of the platform is going to be a normal part of things. For example, even if this bug fix were put into the Cupcake branch as a new release, we have no control over when it would appear on HTC Hero or whatever else devices, so you'll still need to deal with the older version indefinitely. On Wed, May 27, 2009 at 9:18 PM, Jonathan Herriott <[email protected]>wrote: > > I talked to Romain Guy about a bug that is in 1.5 that is a huge bug > (to me) with no good work-a-around that I am experiencing, but I don't > know how many other people will run into the issue (Issue 2773 if > you're interested). I was wondering if I fix the issue myself and > check it in, is it possible to somehow get it in before donut as I was > informed that donut will be out before the end of the year, and I just > can't wait that long. > > As a side note, is it possible to put a process in place, if it does > not already exist, to allow minor bug changes into the current android > stack that the carrier/oem can pick up at their convenience? This way > a person in my position can commit the changes to the current stack > and hope the operator picks it up quickly and pushes it to the user > phones instead of waiting for the next release? > > > -- 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 -~----------~----~----~----~------~----~------~--~---
