Курт вроде - зрелый, опытный человек, а всё в добрый Microsoft верит
По-моему, суть происходящего неплохо раскрыта в публикации 8-летней давности
There’s no place like production. Прежде MS создавал и выпускал корпоративное ПО, которое покупали крупные конторы, ставили на свои сервера и своими силами его поддерживали, иногда обращаясь в поддержку. Если в поддержку обращались слишком часто, то такое ПО переставали покупать. Исходя из этого мышление MS было таким:
Цитата:
What kind of fools build out and maintain useless environments? The kind who got burned building enterprise software. Large businesses rely on enterprise software—it’s got to work or they won’t buy it. Once they buy it, they own it. You don’t get to fix enterprise software anytime you want. That’s right, not even with security patches. Remember, enterprise paychecks depend on having the software run smoothly. Software changes represent risk to an enterprise business. If the software doesn’t work, work well, and continue working well, enterprises businesses aren’t buying it. And they’ll tell you when they are darn well ready to accept a patch.
An entire generation of Microsoft engineers learned the hard way that you can’t release software until the code is fully tested. There are no “retries” in enterprise software.
Теперь MS создает, самостоятельно запускает на своих же серверах и самостоятельно поддерживает
сервисы, поэтому мышление изменилось на такое:
Цитата:
There’s no place like production. You need a development environment to run a small set of automated check-in tests, a test environment to run preliminary acceptance and stress testing to help avoid catastrophic failures, and production. Anything more is superfluous.
The solution is called “continuous deployment.” The concept is simple: deploy multiple builds to production, and use custom routing to direct traffic as desired. It’s like a source control system for regulating services instead of source files. The toughest part is dealing with data, which must function properly across multiple builds. However, if a service is designed to handle at least one rollback after a new build is deployed, even if that new build introduces new data, then that service will function well in a continuous deployment environment.
You deploy your new build to production and test it out. Once verified, you use exposure control to increase the live traffic to your new build by increments — first one percent, then three percent, then 10 percent, then 30 percent, then 100 percent. You monitor service health throughout the process. If your services ever show signs of trouble, you capture the data and route traffic back to your last release (instant rollback).
Т.е. прямым текстом говорится, что тренируются теперь на кошках
Так что да, давайте все вместе работать тестировщиками, сообщать в MS о проблемах и еще платить за использование недотестированных версий. There’s no place like production!