Yep.

Where’s the non-prod test environment? For major systems we always have a multi-tier setup, of Test (pretty open, wild-west, but completely isolated and only test data on it), then Non-Prod Test, which looks a lot like production, has production-like test data, with User Acceptance Testing capability, still isolated from both prod and test. (We also have other layers of test too, say for hardware integration to backend, etc).

Also, this example is why I constantly argue against auto updates for anything, even my phone apps.

Without validation testing, you don’t know shit won’t work and then disrupt your work flow. My phone is a tool that I rely on to work a certain way.

Integration testing is great for release validation.

But there’s also development work that should have been done on the release process itself, like support for progressive rollouts and easy rollbacks.

Principal developer: that’s why we always hav failover, backups, and a rollback plan, and insist on release testing in a staging environment.

Well maybe they just updated too 2.6.1