Release Practices

The team is working on new abilities, addressing new use cases and working on stability and bug fixes on weekly basis.

The information about this process is being laid out in the documentation, including how to manage the release process and help you choose the version that fits you best.

We recommend using the latest version

SDK Versioning

We use semantic versioning to keep track of the SDK version.

Versions are represented in dot-decimal notation, consisting of three decimal numbers in the form of major.minor.patch. For example 1.0.15 indicates major version 1, minor version 0 and patch version 15.

• Major version contains changes that introduce non-backward-compatible change, requiring developer assistance.
• Minor Version contain new features, UI changes and/or new API. no developer assistance is required.
• Patch Version containing only bug fixes, considered as the lowest risk releases, no developer assistance is required.

Release frequency

We aim to release in a very frequent manor, ideally 1-2 times a week.

Deprecation practices

To be filled.