Quoting JBQ from "[android-developers] Re: Cupcake SDKs available for download"
"BTW, I'm very much looking forward to the start of the next Android development cycle, since for the first time in the history of Android such a cycle will start with the source code being openly available. Things won't quite be perfect the first time around, we'll learn from the issues that we are going to face, and we'll all work better together for subsequent development cycles." Having automatically-generated nightly SDK and emulator image builds would be one useful milestone in all of this. Whether those builds are centrally created (e.g., on a Google build farm) or federated via a tinderbox-style system is certainly up for debate. Once we have nightlies, we can do more in the way of recurring smoke tests, so we can get non-developers contributing to see if anything unexpected is broken. Also, green-flagged nightlies might serve in the role of the SDKs that Mr. Sutton is distributing, as interim SDKs developers can test with for application compatibility. I hope the core Android team will reach out to us at "the next Android development cycle", so we can figure out what we can collectively do regarding things like this. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Training: http://commonsware.com/training.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
