Version EOL Policy#
1. Lifecycle Overview#
Our End of Life (EOL) policy is designed to provide a predictable schedule for support and upgrades. The lifecycle of any major version is calculated based on its original General Availability (GA) date.
Key Milestones#
| Milestone | Calculation | Description |
|---|---|---|
| General Availability (GA) | $T_0$ | The date the version was publicly released. |
| End of Maintenance (EOM) | $T_0 + 12$ Months | Final date for bug fixes and security patches. |
| End of Life (EOL) | $T_0 + 24$ Months | Support is no longer provided; documentation moved to archives. |
2. Active Version Status#
Use the table below to determine the current status of your installed version.
| Version | Release Date (GA) | End of Maintenance | End of Life (Support) | Status |
|---|---|---|---|---|
| v2.x.x | 2026-04-10 | 2027-04-10 | 2028-04-10 | Under development |
| v1.x.0 | 2024-03-14 | 2025-04-10 | 2026-03-14 | Active |
| v1.0.x | 2022-05-19 | 2023-05-19 | 2024-05-19 | EOL |
3. Support Scope During Transition#
As a version approaches its EOL date, the level of support shifts:
- Full Support: Covers "How-to" questions, bug fixes, and security vulnerabilities.
- Maintenance Support: No new features. Only critical security patches and high-severity bug fixes are provided.
4. Upgrade & Migration Guidance#
To maintain system integrity and security, we recommend upgrading to the latest Stable Release at least six months prior to your current version's EOL date.
Migration Resources:#
- Breaking Changes Log: Review our Changelog for API or configuration changes.
- Compatibility Matrix: Ensure your OS and hardware meet the System Requirements for the new version.
- Automated Upgrade Scripts: Available for versions the last three releases to simplify the upgrade process i.e. to upgrade to 2.0.0 from 1.14.0 the upgrade would be from 1.14.0 to 1.15.0 to 1.16.0 to 2.0.0.
Warning: Running software past its EOL date may result in compatibility issues with newer OS updates and increased exposure to security threats.
5. Documentation Archiving#
Once a version reaches its EOL date:
- Online documentation will be moved to the Legacy Archive.
- Knowledge Base articles will remain searchable but will no longer be updated.
- Community forums for that version will be set to Read-Only.