That assumes that each sdk is an independent unrelated release, which is not the case. Multiple -FINAL- sdks may in fact be more work, but multiple betas are not - the work done to release rc1 is built upon by rc2, rc3...rcN and the final release.
On Tue, Oct 27, 2009 at 12:25 PM, Marco Nelissen <[email protected]> wrote: > > On Tue, Oct 27, 2009 at 2:14 AM, MrChaz <[email protected]> wrote: >> >> Yeah it would but given it's their job to support the community and >> the community is demanding more maybe they should start to look at >> their practices. > > It's not my job to "support the community", but since I'm obviously > doing so poorly at it, this will be my last post. > In any case, all I meant to say was that the reasoning in the first > message in this thread is flawed: if SDKs are "late "because it's a > lot of work to put them together, then having multiple beta SDK > releases will be even more work, and is therefore likely not going to > result in faster delivery. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
