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?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to