Doing Maintenance outside a scheduled window with no warning is dumb. We use Jenkins in my shop. And we do production testing across a subset of our install base before we push everyone to it. In short we test the hell before anything goes live, then we bash the hell out of it to see that it scales. There is no excuse for a code push that breaks things. If you need App Code with unit tests from your top users say so, many of us could provide code that you could use to test code releases.
2 hours is a LOT of downtime. It will be a LONG time before that works back to 99.95% uptime. My understanding is premier support would not have fixed this for you Jeff. I was doing pitches and demos all day today at Tech Crunch Disrupt, and at VCs. If I had been down today, I would have been off AppEngine. We are already getting on the fence, and have started porting code to make our stuff work on OpenStack in case we need to move for our issues. -- 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.
