Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Shea Bunge

    (@bungeshea)

    Hi @generosus,

    Apologies for the confusion here!

    The Free and Pro plugins are both built on the same core base, and so changes to this core will affect both plugins. In future, we are planning on completely separating them into two individual plugins, but given their shared codebase, we combine the changes together into the one document. Changes that only appear in PRO are signposted to differentiate it from those that only appear in the core (free) version.

    In regards to 3.6.5.1 – this is not a separate version but actually a re-release of version 3.6.5. We tend to stick to a system of only using three numbers to represent a version release– major, minor, patch – and the fourth is only used in cases like this one, where we need to re-release an existing version for some reason. There aren’t any code changes between 3.6.5 and 3.6.5.1 – the updated to the version number it just to ensure that all websites receive the release correctly.

    I appreciate that this could be confusing though – I’m happy to add a line to the changelog indicating that this is what has happened, if that would help clear things up.

    Thread Starter Generosus

    (@generosus)

    Hi @bungeshea,

    Thank you for the explanation.

    Yes, it would be great to add that (i.e., V 3.6.5.1) to your changelog since these posts get buried over time.

    Also, from my learning (and practices) the fourth set of digits in software versioning represents a software build (not a software re-release). This goes along with software versioning practices established by semver.org and other well-known institutions. Software builds are usually not released to the public.

    There are cases, however, where software developers may deviate slightly from the above (with an explanation, such as yours).

    Cheers!

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.