Consider what it was like when web browsers used to be rolled out every 6 months or so. When Google (I believe) started to rollout virtually weekly (or even d

Consider what it was like when web browsers used to be rolled out every 6 months or so. When Google (I believe) started to rollout virtually weekly (or even daily sometimes) updates, there was a bit of a riot from enterprise users. "How will we verify that we can roll out the new browser when you update it so frequently", they said. And then Mozilla followed suit. Eventually people realised that if you roll out an update nearly every day, each update only has a tiny modification in it. You almost never need to validate it. Even if it goes wrong, as long as you can roll back to yesterday's build, you are OK. Having said that, I still think there are projects for which it is best to do it the way you say. I've certainly had a lot of success with that approach as well. As others have said, if it ain't broke, don't fix it.