Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • I can confirm, you fixed this issue in 2.6.30. Thank you very much.

    Yes of course, bugs can happen. I am a developer myself (just different programming language) and I know that Bugs can be introduced. And yes, my company has the same issue as mentioned here. And yes, our next IT included bigger upgrade will come soon, so I won’t file an issue. But if your answer is: “You have to do micro or major upgrades on other plugins, when we introduce a patch level upgrade” I still have to answer: You have a deep misunderstanding about what a patch level version bump is. Even if I just check your changelog (included in your readme) – I think you have a misunderstanding about what a Patch level version bump is.

    https://semver.org/

    Given a version number MAJOR.MINOR.PATCH, increment the:
    
        MAJOR version when you make incompatible API changes
        MINOR version when you add functionality in a backwards compatible manner
        PATCH version when you make backwards compatible bug fixes
    
    Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

    Since you have not just introduced bugfixes – it just does not fit the definition.

    This “frustration” is not about you introduced a Bug. Yes our wordpress admin hit a patch level upgrade and opsgenie alerted me after workhours to fix some service that was down somewhere in our kubernetes. That happens! Just please do not answer on some issue been reported on a patch level version bump: “It is recommended to do all the updates on all the systems” … that just does not fit to the definition of a patch level version bump…

    thanks and cheers

    PS: Thanks a lot for the link to the downgrade. That was totally helpful ??

    • This reply was modified 2 years, 3 months ago by pieck.

    This was a micro version bump… You cannot be serious with this “recommendation”… Please ensure to understand semantic versioning. You should never do only a micro version bump, when you intentionally drop support for previously already working woocommerce versions.

Viewing 3 replies - 1 through 3 (of 3 total)