Skip to main content

How do bug fixes work?


1 comment

  • Propheticus

    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

    Q: The current version used to be a year, but how long does a current version last now?

    A: We are moving to a ‘release when ready’ model which allows us to deliver new features and improvements as soon as they are ready. As such, the length of a version will vary based on the time it takes us to develop each feature.

    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.