Did you just say that Google is not pushing code/releases to tmo and that tmo pulls the public source at random points in time, adds dream specific bits and releases it to end-users? You do realize that all releases till today have come from a closed source project and not AOSP?
(Even if Google doesn't actually push the code/release to tmo, they certainly do tell tmo (and other carriers) when the code in the repo is "stable enough" so they can pull and release. What I'm asking for, is that at this point in time (eg Google has designated the code as "stable enough to release") we get an official SDK - is that too much to ask?) Tauno On Tue, Mar 24, 2009 at 1:47 PM, Mark Murphy <mmur...@commonsware.com> wrote: > > tauntz wrote: >> We need an official SDK - >> and we need it as soon as the tree is stable enough (and way before >> it's pushed to the carriers/end-users) > > Please understand that Android is open source. There is no "pushed to > the carriers/end users" -- hardware manufacturers are welcome to pull > from the tree whenever they see fit. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > Android App Developer Books: http://commonsware.com/books.html > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
