Maybe the releases should be less frequent but the updates more so. If you have a product with 2010, 2015 and 2020 releases but updates on a different delivery frequency / continuous delivery then people can get really excited by all the features in one release over another yet can optionally be continuously updating that release. I don't think that what is happening to SQL Server is that much different. Perhaps the continuous delivery to Azure will come to SQL Server is such a manner.
This used to happen. Then lots of people complained they didn't want features, only patches/fixes. That's where we are. From the MS perspective, to reduce the complexity of too many branches, as well as the reduction of inventory (unreleased features), they've gone to the release cycle of two years, or really 1 now with v.Next due to release this year.
What's the solution? No idea. Some want features, some want patches, some want both. The branch strategy to provide this is crazy. No matter what a vendor does, there are going to be complaints. Keep that in mind. Your choice does not apply to all environments. Releasing SQL Server is close to ordering pizza for 50million people. What toppings work?
Just not pineapple. It's wrong :Whistling:
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!