Yes, this is one of the drawbacks of the 'continuous release' religion. This is largely driven by internal needs, not the needs of the customer the only benefi

Yes, this is one of the drawbacks of the 'continuous release' religion. This is largely driven by internal needs, not the needs of the customer the only benefit for which is some 'new feature' but which they pay the price for in terms of constant 'upgrades' and features jumping around everywhere, documentation completely out of date and other possible integration issues. I think internal release cadence is fine, and 'constant upgrades' for certain subset of beta users, but major release should be just that, and, not required unless necessary. The bureaucracy threshold has superseded the 'useful advances' threshold in most cases and so that should be contemplated by PMs.