SDKs Lifecycle
Understanding and managing the lifecycle of an SDK is crucial for both developers and users. It ensures that the SDKs remain robust, secure, and up-to-date. By clearly defining each stage in the lifecycle, we provide transparency and predictability, enabling developers to plan their integrations and updates effectively. This proactive approach helps prevent potential security risks, reduces the likelihood of encountering unsupported features, and ensures that users benefit from the latest improvements and fixes.
Definition
SDK Lifecycle
The SDK lifecycle encompasses the stages and processes involved in the creation, maintenance, and eventual retirement of an SDK. It is essential for maintaining the integrity and reliability of the software, ensuring that it meets current standards and user needs throughout its lifespan.
End-of-Support (EoS)
End-of-Support (EoS), also known as End-of-Service Life (EoSL), marks a specific point in a product's lifecycle when VGS stops providing technical support. This includes the cessation of bug fixes, patches, and updates. At this stage, while the product may still function, it will not receive any further improvements or corrections, making it crucial for users to upgrade to supported versions.
End-of-Life (EoL)
End-of-Life (EoL) refers to the point in a product's lifecycle when it no longer receives support or updates from VGS. This stage signifies that the product will not be developed further or maintained, and users are encouraged to transition to newer versions to avoid security vulnerabilities and other risks.
SDKs Versioning
All our SDKs, whether for web or mobile platforms, follow a semantic versioning (semver) approach.
This method of versioning provides a clear and structured way to understand the changes and compatibility of different versions:
MAJOR: Releases that introduce new features incompatible with earlier versions. These versions may include significant changes that could affect the existing functionality, requiring users to make adjustments in their code to adapt to the new features.
MINOR: Releases that introduce new, optional features that are backward compatible. These updates add functionality without disrupting existing features, allowing users to benefit from new capabilities without the need for significant changes.
PATCH: Releases dedicated to backward-compatible fixes. These are minor updates that resolve bugs or make small improvements, ensuring the stability and security of the software without altering its overall functionality.
VGS SDKs Lifecycle
The lifecycle of our SDKs can be divided into distinct phases, each with specific characteristics and support levels:
Phase 0. Developer Preview
During the Developer Preview phase, SDKs are not supported and must not be used in production environments. This phase is intended for early access and feedback purposes only, allowing developers to explore new features and provide input before the official release. SDKs in this phase are released as beta versions.
Phase 1. Latest
The Latest phase includes the most recent <major>.<minor> version of the SDK. During this phase, SDKs are fully supported, receiving all necessary updates, including new features, improvements, and bug fixes. This phase represents the period when the SDK is most robust and reliable for production use.
Phase 2. Maintenance
In the Maintenance phase, the focus shifts to providing only bug and security fixes. While no new features are introduced, the SDK remains supported to ensure it continues to function securely and effectively. This phase allows users to continue using the SDK with confidence, knowing that critical issues will still be addressed.
Phase 3. End-of-Support
The End-of-Support phase begins 12 months after the release of a succeeding major.minor version. During this period, limited support is provided, primarily in the form of bug and security fixes. Customers are strongly encouraged to upgrade to a newer version, as this phase signals the gradual phase-out of support.
Phase 4. End-of-Life
In the End-of-Life phase, the SDK is deemed a potential security risk and will not receive any updates or fixes. This final phase signifies that the SDK is no longer maintained or supported, making it imperative for customers to upgrade to a newer version to ensure their applications remain secure and functional.
\
SDK Lifecycle Phase Duration
Our SDK lifecycle model follows a 12-month duration for each phase to provide a structured and predictable timeline for support and updates:
Latest
This is the period during which the latest released version is fully supported, receiving all updates and improvements. The most recent version is denoted by its major.minor version number.
Maintenance
This phase begins 12 months after the latest version is released, focusing on providing bug and security fixes to ensure ongoing stability.
End-of-Support
This phase starts 12 months after a new latest version becomes available, providing limited support as the SDK approaches the end of its lifecycle.
End-of-Life
This phase commences 12 months after the End-of-Support phase, marking the point where the SDK is no longer maintained or supported.
By following this structured lifecycle model, we ensure that our SDKs remain robust, secure, and up-to-date. This approach provides our customers with ample time to transition to newer versions, ensuring their applications remain reliable and secure.
Useful Links
Last updated