Version Numbering Scheme

Before we go any further, let’s talk about version numbering scheme. There is no best practice or set standard that all must adhere to. Rather, each group, company, or team needs to define and standardize their version numbering system.

WordPress uses a three sequence numbering scheme: 4.8.1, where the third sequence is a minor release. I recommend that you read this document, especially if you are going to work in Core.

Other libraries, frameworks, and applications define and use their own numbering scheme.

Take a look at Wikipedia’ Software versioning article. Quickly you’l notice that there are multiple strategies that could be used. Sometimes teams use 4 or 5 sequence numbers. Sometimes they use a product sequence system.

The point is: the version numbering system you use needs to be defined for your team and you.

Strategy

If you are building products (themes and/or plugins), I’d suggest using the WordPress system of three sequence numbers for your releases. But when you’re in development or debug mode, use the asset file’s modification time. I’ll show that to you in the next episode.

If you are building custom websites, you can use anything you want. I use the asset file’s modification time. My stuff is custom for me and for these labs.

Pick a strategy and stick with it.