Have you seen this? http://code.google.com/appengine/docs/roadmap.html
I understand the operational difficulties you're describing. Ideally we would have a way to let early adopters try out the new runtime before we roll it out to all our servers, thus giving us the opportunity to learn about incompatibilities before they became widespread. We've talked about this quite a bit but we don't have anything coming in the near term. As for notification of new server-side deployments, the reality is that we push new code into production all the time. The vast majority of the time nobody notices because we didn't break anything and we didn't introduce any user visible features. If we sent out notifications every time we did this I'm pretty sure you would tune these notifications out within a week or two. Still, if you're running a real service with real users it makes sense that you would want to know about periods of "increased risk" ahead of time. I'm just not sure how we would identify those for you. The trick with a new SDK is that we can't release it until we've updated our servers with new code that is prepared to handle the new SDK, and by that time, if we've goofed and introduced an incompatibility, your app has already run into it. I suppose we could make the SDK available ahead of time in some form where it can only be run locally, but I can imagine it being pretty confusing to have an SDK that is only half-functional. What do you think? Max On Thu, Nov 5, 2009 at 7:44 PM, Roy Smith <roy.smith....@googlemail.com>wrote: > 1.2.6 broke a few items based on the posts in this group and was > implemented with no prior notice. > > Had we known what the changes were, and were given a couple of day's > notice, we could have been monitoring our live apps and reviewing our code > for incompatibilities, implemented some contingencies, downloaded the new > SDK and locally regression tested our apps, etc. > > As it happened, the first that many of us knew of any problems was when > live users complained to us. We then waste a bunch of time looking for > problems, only to subsequently learn that a new SDK/API had been deployed. > > So my concern is operational rather than around any design/development > decisions. I'm not asking for a firm date, just a couple of day's notice > > Having said that a roadmap would be extremely welcome :-) > > best > Roy > > > On Fri, Nov 6, 2009 at 3:36 AM, Max Ross (Google) < > maxr+appeng...@google.com <maxr%2bappeng...@google.com>> wrote: > >> Hi Roy, >> >> I don't have a firm date to give you on the next release because we're >> going to test it until we're satisfied with the quality. The release will >> be backwards compatible with the current release. What sorts of decisions >> are you looking to make based on the release date? Maybe there's some other >> way I can help you with them. >> >> Max >> >> On Thu, Nov 5, 2009 at 6:09 PM, Roy Smith >> <roy.smith....@googlemail.com>wrote: >> >>> On Thu, Nov 5, 2009 at 9:17 PM, Max Ross (Google) < >>> maxr+appeng...@google.com <maxr%2bappeng...@google.com>> wrote: >>> >>>> The next SDK (1.2.8) is working its way through QA right now so >>>> hopefully it will be available in the next week or two. >>>> >>>> >>> Please can we get a bit more notice on the changes and the make-live date >>> than we did with 1.2.6 >>> >>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
