We understand how important it is that you can rely on your tools. That's why our number one priority is to create high-quality software that works. Our number two priority is to fix bugs quickly when we find them, minimizing any disruption to your work.
Each time we find a bug or you report one, we assess the severity and the number of users impacted. We consider bugs to be major when they prevent you from using the software or core workflows. These will always be fixed and are free, regardless of your software version.
- If you are on the latest software version*, you will receive all bug fixes for free
- If you are on an older version, you will receive all major bug fixes for free
*We consider 15.4, 16.1, 16.2... to each be a version.
So for those understanding semantic versioning (Major.minor.patch e.g. 15.4.2) : you pay for each minor version and get free patches (containing bug fixes) only until a next minor is released. Unless a bug is considered major and "prevent[s] you from using the software or core workflows", where what is considered a core workflow is left undefined.
A minor release is also called a feature release.
combined with the FAQ answer
This means we can expect a couple of minor versions (feature releases) a year. Conclusion: instead of nearly a year of bugfixes which was already on the short side, now you will only get a couple of months worth. In my opinion this is an unprecedented (and unacceptable) short support life-cycle for a piece of software in this price-category.
What would help is feature toggles: allow perpetual license holders to receive bugfixes that come after/with feature releases but switch off the new features they have not paid for. This way you can at least support a major version until a next major. Meaning toggles are only needed for new features since last major.
Please sign in to leave a comment.