Back in the day, Release Often was a contract between the developer and the individual/single customer. Today it means the entire end-user base. That means every time there is the smallest update a few hundred million/billion downloads begin and basic productivity is halted for the next 30-60 minutes and if you’re lucky it has not interrupted or broken anything important.

My development lab contains nearly 40 discrete computers…. OSX, multiple Linux distros, OpenBSD, ChromeOS, DSM, and a couple of managed firewalls, routers and SIP servers. And when they get a ZERO day patch I’m all over the place trying to get these systems working again. And each requires a human to complete the task. It would be great to have one OS on a monster system but that has it’s problems too.

Releasing too often has it’s problems too.