Bad versioning

  • Resolved eclev91

    (@eclev91)


    3 years, 1 month ago

    Hey team –

    Back at the 1.5 release, you changed your versioning syntax. You went from 1.49 to 1.5.0.

    1.49 is technically greater than 1.5, so any logic that depends on something like PHP’s version_compare function won’t return what I wager are the expected results.

    You would have to release version 1.50 to get back on track. Or 2.0.

    Specifically, this affects WPackagist and any setups leveraging Composer to require this plugin. It doesn’t install the latest release by date, it installs the latest release by tag, which is 1.49.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author richplugins

    (@richplugins)

    Hi @eclev91,

    First of all, thank you very much for improving the plugin, it’s really great to hear from our users!

    Yes, we know about this issue, because already faced this 2 years ago and unfortunately, it’s our fall.

    However, at the moment we are preparing a major plugin update and we can choose the version in such a way as to kill two birds with one stone, firstly, to solve the current problem, and secondly, to make the next one really.

    If you know, it will be great for help! If we will called the version like 2.0 it will be greater then 1.9.9 and 1.49? And if so, can we release the next version like 2.0.1?

    Or we can make the version 2.0.0 right away?

    Thanks!

    Thread Starter eclev91

    (@eclev91)

    Howdy @richplugins,

    To answer your question:

    The entire X.Y.Z versioning system is based on something called semantic versioning. Per the guidelines for semantic versioning, you should only cut a 2.0.0 release if you’re making backwards-compatibility breaking changes to the “public API”, whatever you determine that is for your plugin.

    If you wanted to cut an immediate release simply to fix the versioning issue, I would cut version 1.50.0, which would be greater than 1.9.9 and 1.49. You wouldn’t even have to change any of the plugin logic. Simply update the version.

    I would not cut a 2.0.0 release until you have this new major update ready.

    But technically, those are just guidelines. Even WordPress core doesn’t really follow semver, which I personally find frustrating.

    • This reply was modified 3 years, 1 month ago by eclev91.
    Plugin Author richplugins

    (@richplugins)

    Hi @eclev91,

    I think the best way is released a version 2.0, it will greater then 1.49 and 1.9.9. Then we can use semantic versioning as well started from 2.0.1.

    Thank you for your help!

    Plugin Author richplugins

    (@richplugins)

    Hi @eclev91,

    We’re glad to announce that release 2.0 is available for update.

    Please let me know if you have any issues or question according to this.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Bad versioning’ is closed to new replies.