Move To Semantic Versioning Complete

If you’ve never heard the term “semantic version”, don’t feel bad – most end users of software have never heard the term either. But more and more, software is using the concept to govern the release numbers that are assigned to new public releases.

In the case of Simple:Press, we’ve completed our to move to it with the updates we’ve pushed over the last 60 days. All our core products now sport a tri-level version number and should adhere to the semantic versioning guidelines going forward.

About Semantic Versioning

Semantic Versioning is a scheme that can help users figure out the likely impact of an update just from the version number of a new release.

Put simply, semantic versioning requires the use of a tri-level version number in the form of an x.y.z format. Based on which level of the number changes, you can get a pretty good idea of the effect an update might have on your system.

If only the last number changes (“z”), then the new release only includes bug fixes. For example, if the current version of Simple:Press is 6.1.0 and the next version is 6.1.1, then its a fairly good guess that we did not deliberately include anything that would break existing functionality in 6.1.1 (i.e.: the release should be 100% backwards compatible with version 6.1.0).

If the middle number changes (“y”), you can expect some new functionality but nothing that breaks existing functionality. So, using the example above, version 6.2 of Simple:Press is likely to have some new functions in it.

If the first number changes (“x”), you can expect major changes in the product and likely some things that will break backwards compatibility. You saw this when we moved from 5.0 to 6.0 of Simple:Press. Many of you are still running on 5.0 because there are major backward compatibility changes in 6.0.

Overall, the idea is simple, right? And I bet that over the years you’ve probably intuitively read new version numbers that way. The Semantic Versioning standard is simply a way of formally expressing what you’ve probably intuitively felt when reading software upgrade notes!

If you’ve recently upgraded your Simple:Press plugins and themes you will see that they all now sport a tri-level version number – prior releases only included two levels.

Learn More About Semantic Versioning

You can learn more about the intention behind this idea of tri-level version numbers at

Read Next

Did you find this article useful? Or do you use Simple:Press today?  If so, please support Simple:Press with a review on  Every review goes a long way towards bringing other users on board!

Click here to review Simple:Press on

More From Simple:Press

What’s New In Simple:Press Forums 6.6.0

September 9, 2020

Simple:Press Forums 6.6.0 introduces two new major features and a lot of improvements to one of the existing features. And, of course, some bugs were stomped.

Read More

How We Increased Performance On Our Site By 300%

July 4, 2020

A few days ago we moved our site from Liquid Web to our new FireupWP and WPCloudDeploy project platform. This new platform allows us to use dedicated cloud VMs from places like Digital Ocean, Linode and Vultr. We pay the cost of the VMs with no markup which provides huge savings over regular hosts. We…

Read More

New Simple:Press Forum Theme: Modern 2020

March 5, 2020

A new default theme is coming to Simple:Press Forums with the release of Simple:Press Forums 6.5.0. Features of this theme: More modern looking with larger default font sizes and button sizes. Less use of tiny icons More color customization options Better display on mobile More white space Just like our previous default theme, Barebones, you…

Read More

Now Available: SPMS Version 2.7

January 10, 2020

Version 2.7 of Simple:Press Member Subscriptions is now available. It includes more than two dozen fixes and tweaks.

Read More