I imagine version numbering has been used in so many different ways by plugin authors and coders across the web, so I figured I’d clear up the confusion for anyone wondering how we version the Pods plugin.

Let’s start with the structure, MAJOR.MINOR.PATCH

As you can see above, the first number is the MAJOR numbering, which can increase to be any number of digits. The next numbering is for MINOR versions, which are increased when a new feature is added, or when a new MAJOR version is released, it’s reset to zero (0). The final numbering is for PATCH versions, which should strictly include only bug fixes and patches. This also is reset to zero (0) when a new MINOR version is used. The standard is to reference MAJOR.MINOR versioning for primary releases, like 2.0, or 2.1, etc.. as when there are two zeros (0) next to each other it usually makes it cleaner to reference only the first zero (0). Instead of 2.0.0, we are using 2.0, and not strictly just the number two (2).

• RIGHT: Pods 2.0
• WRONG: Pods 2
• WRONG: Pods 2.0.0
• RIGHT: Pods 2.0.1
• RIGHT: Pods 2.1
• WRONG: Pods 2.1.0
• RIGHT: Pods 2.1.1

You get the picture. Well, hope I helped clear some stuff up, but basically if it takes us longer to get through the upcoming Alpha / Beta release phases, we’ll likely see Pods 1.10 and Pods 1.10.x versioning (and so on).

Prior to 2.0, we were using a slightly modified version of this because our internal versioning / upgrading code did not support it. So what 1.x has been using is the following structure, MAJOR.MEDIUM.MINOR.PATCH where MINOR is used to denote new features, and MEDIUM is used to denote larger new features.