Verj.io Versions
Verj.io Version Releases are supported for two years after the first major iteration of their Verj.io Version. For example, we will support Verj.io On-Premises v5.11.x for 2 years after v5.11.0 was released.
The final Major Version in a Landmark Series is supported for 3 years after the initial iteration of that Major Version. For example, if v8.0.0 was released then v7.6.x would be supported for three years after v7.6.0 was released (if v7.6 is the latest Verj.io Version of the v7.x.x Landmark Series).
The most recent Verj.io Version Release is never considered to be end-of-life until it is replaced with a new one at which time it reverts to the rules outline above.
The end-of-life dates are:
- v5.10 and all previous versions are unsupported.
- v5.11: released July 2022 has an end of life of 31st July 2024.
- v5.12: released January 2023 has an end of life of 31st January 2025.
Ebase Technology does not provide support, advise on workarounds, or provide fixes (including security fixes) for Verj.io products that have passed their end-of-life date. Customers are required to upgrade to a supported version. Issues raised prior to a version’s end-of-life date, but still unresolved, will only be addressed in currently supported versions.
We do not support end-of-life Verj.io products interacting with supported Verj.io products, for example, an end-of-life Verj.io Studio deploying to or testing against a supported Verj.io Service Plan.
Feature, Service, and JavaScript API function End of Life
- Features, services, and API functions that have been marked as deprecated may be removed in the next-but-one Major Version Release to the one in which the deprecation initially occurred. For example, if a feature was deprecated in version v5.7.2 it may be removed from the product in version v5.9.0.
- In exceptional circumstances a release may remove non-deprecated features, services and/or JavaScript API functions.
- Landmark Series Releases may substantially change the product and like-for-like features, services and functions may not be possible.
Verj.io Cloud
Verj.io Service Plans may only contain supported Verj.io Application Containers.
End-of-life Verj.io Service Plans may be suspended or automatically upgraded at our discretion. Note that in the case of upgrading we cannot test or otherwise guarantee your application still performs as expected after the upgrade.
All Verj.io Service Plans are upgraded to the most recent Verj.io Version Release by Ebase Technology in a timeframe that enables users to test and prepare their Verj.io Application for the new Verj.io Version Release. We endeavour to minimise any downtime for your Verj.io Service Plan.