09-05-2018, 04:58 PM
Starting from 3.0.0, Curvy is using the versioning standard “Semantic Versioning 2.0.0”. This was done to make it clear to users what changes to expect just from looking at the version number. More about Semantic Versioning 2.0.0 here : https://semver.org/
In a nutshell, and given a version number MAJOR.MINOR.PATCH:
- An increase in MAJOR is done when there are non backwards-compatible changes.
- An increase in MINOR is done when there are backwards-compatible changes that adds new features/API member, or modifies existing ones.
- An increase in PATCH is done when there are backwards-compatible bug fixes.
Whenever a number is increased, the numbers to its right are set to 0.
In a nutshell, and given a version number MAJOR.MINOR.PATCH:
- An increase in MAJOR is done when there are non backwards-compatible changes.
- An increase in MINOR is done when there are backwards-compatible changes that adds new features/API member, or modifies existing ones.
- An increase in PATCH is done when there are backwards-compatible bug fixes.
Whenever a number is increased, the numbers to its right are set to 0.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
