🤝

Support Policy

Versioning strategy

The iAdvize Messenger SDK follows Semantic Versioning, that means that given a x.y.z version number:
  • releasing critical bug fixes will change the z number: 3.4.5 -> 3.4.6 (PATCH release)
  • releasing non-critical bug fixes or backward-compatible new features will change the y number: 3.4.5 -> 3.5.0 (MINOR release)
  • releasing anything breaking the SDK public API will change the x number: 3.4.5 -> 4.0.0 (MAJOR release)
As versioning may differ from a platform to another, each iteration is given a codename so that it is easier to find the corresponding SDK on another platform.

Support status

iAdvize Messenger SDK support comes in several distinct status:
  • Full support: the SDK will receive bug-fixes and new features on a regular basis. MAJOR, MINOR and PATCH versions can be released upon it.
  • Partial support: the SDK will receive security bug-fixes. Upon this version, only PATCH releases will be made, no MAJOR or MINOR. Update to the latest SDK is advized.
  • No support: this SDK version is not supported anymore, update to the latest SDK is mandatory and unstable behaviours may occur during the use.

Release support lifecycle

When a new MAJOR version is released, the previous MAJOR version enters a grace period of 24 months, at the end of which it reaches its end-of-life. After that moment, no support is provided on this version.
The latest release (most recent MAJOR.MINOR) is the only version that is fully supported by iAdvize.
In addition, several versions benefit from a partial support:
  • the last 3 MINOR of the current MAJOR
  • the last MINOR of previous MAJOR still in grace-period

Supported versions

Platform
🟢 Full support
🟠 Partial support
🔴 No support
Android
2.11
2.10
2.9
2.8
Every other version
iOS
2.13
2.12
2.11
2.10
Every other version
React Native
3.3
3.2
3.1
3.0
Every other version
Flutter
2.12
2.11
2.10
2.9
Every other version

Hybrid plugins

Please be aware that this only applies to the native iAdvize Messenger SDK (Android & iOS). Even though the hybrid plugin wrappers may have semantic versioning that differs from the native SDK, their support is dependent on the native SDK version they embed.