3 ms·

And now they've released 3.0.0 in their cloud, which they claim is backwards compatible, but lets see. I sometimes wonder if vendors realize that they put thei

And now they've released 3.0.0 in their cloud, which they claim is backwards compatible, but lets see. I sometimes wonder if vendors realize that they put their customers into a buying mode when they do this, when our options are: - Upgrade to the new version of product X. - Change to vendor or tooling completely as we're already changing everything. We might pick another system if we feel like it is more stable.

flagrant_taco 3y ago
If it's backwards compatible why would they bump the major version? Either there should have been a breaking change in there or they don't understand symantic versioning
- flagrant_taco 3y ago
  Not sure why the downvotes here, a database service misusing semantic version is itself a red flag in my opinion. If major releases don't indicate a breaking change I'm not as confident in what might be part of a minor or patch release.
  - sofixa 3y ago
    To be fair, they have a bunch of associated tooling like their query language and UI, so it might have been those that have merited a bump to 3.x
    - flagrant_taco 3y ago
      Yeah that could be, but I think that would still only merit the bump it there was a breaking change in the public API