7 Responses

  1. David
    David October 12, 2018 at 13:21 | | Reply

    You’re doing it wrong. Before the relaunch the version was 2.2.5.
    This new version breaks backwards compatibility, as you said it’s been written from scratch… That makes it version 3.x

    You’ve missed the entire point of semantic versioning… The numbers are supposed to mean something just by looking. V2 is newer than v1, and breaks backcompat. But now 0.x is newer than 2.2.5, and in 2 API updates from now, you’ll have a 2.0.0 that’s newer than 2.2.5

    You really thought this was a smart idea?

    1. Miguel
      Miguel October 13, 2018 at 03:45 | | Reply

      Hi David – I’m a developer for this plugin. Thanks for the feedback. I’d like to elaborate a bit because I think that this post might be a bit misleading.

      We did not “relaunch” the product and while we may say that we’ve (re)written it from scratch, that’s not entirely true either. It’s just an easier way of explaining it.

      The truth is that the old EDD Bookings plugin is not a product that we sell, provide support for, maintain and market. It’s been discontinued.

      The new EDD Bookings is quite literally a new product that just bears the same branding. We re-used nothing else, not even the repository and Composer package. In fact, it is almost impossible to update from the old to the new and you can even have both installed at the same time since they don’t even share the same plugin directory name and PHP namespace. That’s how different they are.

      This is a natural application of SemVer; a new product begins its life at version 0.1.0 and that version grows depending on the changes that go into it.

  2. Anton
    Anton October 13, 2018 at 03:51 | | Reply

    I would disagree with that definition of the numbers. So, if a product is at version 1.0 , does that mean that it received 0 patches, and had 0 improvements? I don’t think so.

    1. Miguel
      Miguel October 14, 2018 at 03:59 | | Reply

      Ah true! The definitions for patch and minor should then include “since the last [minor/major] version” respectively.

  3. Rajkumar
    Rajkumar October 20, 2018 at 00:36 | | Reply

    It is an interesting article to read on. I always thought about the version numbering system when there was a new update in WordPress and it always confused me a lot. But now after reading your article, I understand all the logics behind it. You simply clear my doubts regarding the same.

    According to me, SemVer versioning is the best way to describe the version numbering system. Also, I totally agree with Anton’s comment which states that how can be a product or plugin can be made with zero patches and no scope of improvements? Thanks for sharing this.

Leave a Reply