I'd support a 5-day update windows between rounds. It would not look great for an app to make it to the top 200 from the first week of voting, but then do nothing but crash in the 2nd round. Besides allowing people to test and fix 1.6 issues, it would also ensure the top 200 are fully polished and reflect well for the Android platform.
However - I can also see people who might view the above as unfair as well. It is the question without an easy solution - now that 1.6 is out, what would be the best course of action Google could take besides staying the course? On Oct 2, 12:05 pm, Spencer Riddering <[email protected]> wrote: > It's only a week into the ADC2 judging and already phones are being > updated to Android 1.6 Cupcake. With at least one more week to go in > the first round and (I'm guessing) two more weeks of judging in the > second round this means that around 75% of the ADC2 judging will occur > on Android 1.6. The 1.6 SDK was not made available to developers until > after the ADC2 deadline so (except for a few exceptions) all of the > ADC2 applications were not tested on this judging platform. > > Already an undocumented change in 1.6, which can break applications > that worked on 1.5, has been discovered > herehttp://groups.google.com/group/android-developers/browse_thread/threa... > and Google has acknowledged the problem > herehttp://groups.google.com/group/android-developers/browse_thread/threa... > > Why is Google allowing an estimated 75% of the ADC2 to be judged on a > platform version that almost no one has had a chance to test on? > > Spencer Riddering --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
