Incorrect versioning

#1

Just letting you guys know that if you are trying to use Semantic Versioning, you are using it wrong. You have the major version set to 1, and yet are still making backwards incompatible changes to the public API on minor version changes (going from 1.0 to 1.1). In semantic versioning, you can only do this when the major version is 0.

From http://semver.org/

rule 4: Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

rule 7: Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

rule 8: Major version X (X.y.z | X > 0) MUST be incremented if any backwards incompatible changes are introduced to the public API. It MAY include minor and patch level changes. Patch and minor version MUST be reset to 0 when major version is incremented.

If you aren’t trying to use Semantic Versioning, could you please define what system you are using to increase the version numbers?

#2

We are not strictly following the semantic version x.y.z as it is commonly defines, as we want to keep the major x = 1 until Paradox is out of beta, so we are currently using the minor (y) to introduce breaking changes. So all 1.y-beta should introduce some breaking changes but hopefully the more we advance our minor version, the less we will have breaking changes. Once we are out of beta (It will take around one year from here), we will use major version for breaking changes.