There was a problem with a non-backwards compatible change in db.Model constructor as well. That could have been caught by releasing the sdk early.
On Thu, Oct 15, 2009 at 4:25 PM, dflorey <[email protected]> wrote: > > Hmmm. I guess this is complicated. > The problem with cancelled background tasks was not in the sdk but in > the appengine backend. > The only option to test things in advance would be to have some kind > of sandbox with the latest backend plus some dev previews of the sdk > to try out the new sdk/backend combination. > I have no clue if this is feasible as developers may need their actual > datastore data. > But of course it would be great to have some kind of staging process. > > Daniel > > On 15 Okt., 16:01, Joshua Smith <[email protected]> wrote: > > GAE Team, > > > > A simple lesson-learned from the 1.2.6 fiasco is that you have your > > release process backward. > > > > What you *should* be doing is: > > > > 1) Release the new version of the SDK to developers > > 2) NOTIFY developers that there is a new version and it *will* be > > going live in X days > > 3) Let the developers tell you about all the problems, and help them > > find work-arounds, or do an update if necessary > > 4) Update the servers > > > > This is the way Apple releases new JDKs, for example. That way, the > > developers have a chance to find all the bugs *before* millions of > > people are bitten by bugs introduced by framework changes. > > > > -Joshua > > > -- Alkis --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
