For versioning, we uses the Semantic Versioning (SemVer) convention: major.minor.patch. Basically, the schema that the Equo SDK follows is:
Every time there are incompatible API changes the major version is incremented,
adding backwards-compatible functionality increments the minor version and,
backwards-compatible bug fixes increment the patch version.
When a breaking change added to the SDK API exists, a major release will be published. Major releases will occur roughly every 6 months and may contain breaking changes. Several release candidates will be published prior to a major release in order to get feedback before the final release. And also an outline of what is changing and why it is chaning will be included with the release candidates.
Every time a new feature or an API change is added that is not breaking backwards compatibilty, a minor release will be published. Tests are developed before a new release happens and to have the confidence that that release is going to be great, however, with new code comes the potential for new issues. We are scheduled to release a minor version monthly, if any features or API changes were made.
Every time bug fixes are added, and the API has not changed and no breaking changes were introduced, a new patch release will be published. It is scheduled to release path releases weekly, but it can vary. Patch version releases will always be released prior to a minor release in order to ensure that the patch release can fix existing code without introducing new issues from the new features.