I agree with you but a Service Pack should suffice esp. right after you've release a full new version/update to a major product/tool like VS.
I'm pretty sure I can upgrade to a service pack. Changing versions, OTOH, probably requires approval from management.
Two things are apparent: 1) The problem you are addressing is a management problem in your organization, not a problem with Microsoft releasing a new version of VS. 2) You aren't the decision-making customer for Microsoft VS at your organization, so even the problem you had was with VS, it wouldn't necessarily be a problem MS would have much incentive to address.
That's what service packs are for. With a product that has as big a footprint as Visual Studio it will be impossible for shops to keep up with the annual versions. Many will simply delay updates. Ironically, increasing the speed of major release may actually delay the introduction of some improvements by customers.
Ahem... I am. I would much rather have smaller more frequent updates to important tools than huge disruptive ones. Short feedback loops are a good thing.