From Piwik 2.1.0 Piwik will exclusively use Semantic Versioning for our version numbers.
For Piwik Core
That means that our new version will be Piwik 2.1.0 and not Piwik 2.1. We will always use 3 numbers in the version string.
For Piwik Plugins
All plugins in the marketplace are using Semantic Versioning. When a new plugin version is released, the marketplace will check that the version number is a valid Semantic Version.
Why Use Semantic Versioning?
Without compliance to some sort of formal specification, version numbers are essentially useless for dependency management. By giving a name and clear definition to the above ideas, it becomes easy to communicate your intentions to the users of your software. Once these intentions are clear, flexible (but not too flexible) dependency specifications can finally be made.
More info http://semver.org/
Note: we may not increase MAJOR number when introducing backward incompatible platform changes (such as in Piwik 2.1.0) because we are in a fast iterating cycle and this may happen often as we improve the platform and architecture of Piwik.
From Piwik 2.1.0 Piwik will exclusively use Semantic Versioning for our version numbers.
For Piwik Core
That means that our new version will be Piwik 2.1.0 and not Piwik 2.1. We will always use 3 numbers in the version string.
For Piwik Plugins
All plugins in the marketplace are using Semantic Versioning. When a new plugin version is released, the marketplace will check that the version number is a valid Semantic Version.
Why Use Semantic Versioning?
Without compliance to some sort of formal specification, version numbers are essentially useless for dependency management. By giving a name and clear definition to the above ideas, it becomes easy to communicate your intentions to the users of your software. Once these intentions are clear, flexible (but not too flexible) dependency specifications can finally be made.
More info http://semver.org/
Note: we may not increase MAJOR number when introducing backward incompatible platform changes (such as in Piwik 2.1.0) because we are in a fast iterating cycle and this may happen often as we improve the platform and architecture of Piwik.