Are you doing dream builds or emulator builds? FYI I haven't discontinued my dream builds - I've been focusing on the work some people have done to get actual, working google services into master. (And it seems like despite the opening of donut and the claimed 'real soon now' release of cupcake, they have recently merged in a bunch of changes that break basically everything. Audio, make/break calls, etc are all broken in the newest trees.)
Do you have plans to integrate unapproved fixes? (Either fixes in the review system that aren't pushed to the tree yet, or fixes that didn't make it there to begin with.) That has been a fairly standard problem with these builds - since most of the google devs don't use the external tree, it is frequently out of sync or just flat broken. (EG the recent merge of opencore 2, when the internal cupcake tree is still written to use opencore 1.) And if you are trying to do dream builds, its even worse - updated hw support binaries, etc. (For those few remaining people who don't know :) my g1 cupcake/master builds are at http://andblogs.net/images/snapshots. 3/16 is reportedly quite stable.) On Fri, Apr 10, 2009 at 8:01 PM, Mark Murphy <[email protected]>wrote: > > A few folk are starting to build the infrastructure for a nightly build > farm, to extend Al Sutton's groundbreaking work on creating downloadable > SDKs out of the public Android repositories. > > It will take some time for us to get everything together, including > working out the kinks in the Android development process itself -- see > David Turner's post on this thread: > > > http://groups.google.com/group/android-developers/browse_thread/thread/1e5d4f6dfef96c70 > > What we are looking for now are two types of volunteers: > > 1. If you would like to contribute time -- personal and CPU -- to > building Android itself, sign up to operate a build slave. This > basically means you'll provide a PC or VPS that can build Android from > the latest sources on demand. "On demand" will be nightly, more or less. > The more volunteers we get, the fewer times any given build machine will > need to actually be doing a build. > > 2. If you are interested in running the buildmaster -- a BuildBot or > Hudson server that coordinates the builds and publishes their results -- > sign up for that. > > If nobody else signs up, I will run the buildmaster on the CommonsWare > slice at Slicehost, and I will provide an initial build slave here at > CommonsWare HQ. However, we could really use more build slaves. Also, > I'm a rookie at running a buildmaster -- to paraphrase Hobbes, my work > on that will be nasty, brutish, and slow. If you're better at it and > want to take on that task, sign up! > > Eventually, of course, we'll need people to play with the build results, > but right now, a buildmaster and build slaves are what's needed. > > If you are interested in either role, or if you think there is some > other near-term role you'd like to play in this effort, reply on this > thread or contact me off-list, and let me know specifically what you'd > like to do. > > Thanks for everyone who's provided advice to me on this topic so far, > and thanks in advance for everyone who joins the build squad! > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 2.0 Available! > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
