Semantic Versioning and Old Versions

UniTween now uses Semantic Versioning. This means that version numbers now have a standarized logic, providing users a better understanding of what each version changes only by looking to the version number. Here's a summary of how Semantic Versioning works:

Given a version number MAJOR.MINOR.PATCH, increment the:

• MAJOR version when you make incompatible API changes,
• MINOR version when you add functionality in a backwards-compatible manner, and
• PATCH version when you make backwards-compatible bug fixes.

To adapt into this change, all previous version numbers have been slightly adjusted. The only change was the removal of "1." of every version before this change. Here's a list of all changes:

• 1.0.4.0 -> 0.4.0
• 1.0.3.0 -> 0.3.0
• 1.0.2.3 -> 0.2.3
• 1.0.2.2 -> 0.2.2
• 1.0.2.1 -> 0.2.1
• 1.0.2 -> 0.2.0
• 1.0.1 -> 0.1.0
• 1.0.0 -> 0.0.1

Note: As UniTween is currently not yet in 1.0.0, the Semantic Versioning rule below is very important (if a compatibility issue arises, this will be documented into the Changelog, read it before upgrading your version):

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