No worries Tom, I understood you weren't specially aiming anything at me. One of my concerns of the current scheme is patch migration. With donut, éclair, and flan having feature fall overs and master taking commits as well it could easily end up with checkins' and merges to several branches just for one piece of code, so although it may be great now it could be a beast to tame in the future.
The Android dev blog does seem a bit underutilised, but I agree it would have been a great way to clarify things at an earlier date. Al. -- * Written an Android App? - List it at http://andappstore.com/ * ====== Funky Android Limited is registered in England & Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. From: [email protected] [mailto:[email protected]] On Behalf Of Tom Gibara Sent: 27 July 2009 09:57 To: [email protected] Subject: [android-discuss] Re: What is Donut? Just to be clear, my grumpiness wasn't aimed at your effort to clarify things, but at the rumour mill that makes it necessary - having just read my post, that may not have been clear. Basically, I think the source tree should be managed in whatever way is most efficient for the team doing the development and which establishes android as a sustainable OS project. I don't think PR concerns should be allowed to impinge on that decision. Perhaps if short, timely clarifications could be posted on the Android developer blog, that might help to counteract the spread of incorrect information (or perhaps not - King Canute comes to mind). Tom. On Jul 27, 2009 8:47 AM, "Al Sutton" <[email protected]<mailto:[email protected]>> wrote: I think the biggest confusion is that given the Google IO demo and the statements from Andy Rubin any people assumed that the donut release feature set had been fixed, and so the donut tree was working towards that feature set. What's come to light is that the donut release feature set hasn't been fixed, and so donut is more a dev tree than an alpha, beta, or rc quality tree at the moment. The main reason the Google guys have got involved is some (very useful) expectation management. The more stories that circulate about multi-touch and other candidate features in donut the more likely consumers will hear them and expect those features, and when they don't arrive consumers will get disappointed. If Google PR had got onto people like engadget when they published this http://www.engadget.com/2009/05/27/android-2-0-donut-features-demoed-at-google-i-o/ nearly two months ago the donut == 2.0 mistake boulder wouldn't have got so much momentum. My suggestion for tackling it would be run the trees in a similar way to cupcake appeared in the open source tree; that is create an éclair tree when the éclair release feature set is fixed, and once the feature set is fixed the éclair tree only contains the work done in implementing it, that way éclair tree == éclair release (once its' done), the head of the tree can keep all the latest dev work in it, and the confusion is minimised. Al. -- * Written an Android App? - List it at http://andappstore.com/ * ====== Funky Android Limited is r... From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Tom Gibara Sent: 27 July 2009 08:26 To: [email protected]<mailto:[email protected]> Subject: [android-discuss] Re: What is Donut? Sorry if this sounds a bit grumpy (I've been up since 3am) but: 1) How is this different from what one might sensibly expect as a developer? I appreciate tha... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
