3 ms·
Just a quick preview...we will be posting a blog post tomorrow morning with an update. Because of the delayed final blog post, we are delaying things by one wee
by ptoomey3 9y ago
Just a quick preview...we will be posting a blog post tomorrow morning with an update. Because of the delayed final blog post, we are delaying things by one week. The plan is to do a 1hr brownout on February 8th, followed by a permanent deployment on February 22nd. We realize that no matter how much notice (announced roughly a year ago), there are bound to be some systems that are both incompatible and unknowingly running on production systems. So, the hope is that a 1hr brownout will help to unearth such systems and give folks time to get them updated.
- akrasuski1 9y agoThat is honestly a great idea for safe-ish deprecation in uninformed environment!
- Klathmon 9y agoI always loved a similar idea that I believe Google uses (or used at one point) for sunsetting APIs. You start by making 1% of requests fail on the scheduled date, then gradually increase that percentage over time until 100% of requests are failing. This gives anyone that doesn't follow your blog or news to start realizing that there's a problem and find a solution before it completely cuts off. I personally feel a brownout of 1 hour will barely register as a blip at many places, and if it goes back to working 100% they are liable to just ignore it after it resolves itself.
- myelin 9y agoLast time we deprecated something in App Engine, we made an "opt out" flag, that customers could manually flip to keep the old way working for another week. This was reset every 7 days, until the final switchoff date. This worked pretty well; we saw fewer and fewer customers opting out as everyone updated their code, and the final deadline didn't come as a surprise to anyone.