Verj.io products are released at a particular Verj.io Version that follows the following nomenclature: v[landmark].[major].[maintenance], e.g. v5.10.2.
Veri.io products with the same Verj.io Version have been designed to be used together. For example, Verj.io Studio v5.10.2, Verj.io On-Premises v5.10.2, and Verj.io Gateway v5.10.2 are all designed to work together.
Verj.io Service Plans have a Verj.io Version that indicates the version of its Application Containers. Verj.io Application Containers are functionally equivalent of Verj.io On-Premises at the same Verj.io Version. Verj.io Service Plans are designed to work with other Verj.io products at the same Verj.io Version. For example, Verj.io Service Plans that have a Verj.io Version of v5.10.2 are designed to work with Verj.io Studio v5.10.2 and Verj.io Gateway v5.10.2.
Although we endeavour to maintain backwards compatibility, we can’t guarantee that using Verj.io products of different Verj.io Versions together will work as intended.
Landmark Series
A new Landmark Series may fundamentally alter all or part of the product. Adapting and testing your Verj.io Application before upgrading a production environment to a new Landmark Series is crucial.
Landmark Series iterate the Verj.io Version’s landmark component, for example v5.x.y -> v6.0.0.
Major Version
Major Versions may introduce, alter, and occasionally remove features and services. Testing your Verj.io Application before upgrading a production environment to a new Major Version is recommended.
Major Versions iterate the Verj.io Version’s major component, for example v5.9.x -> v5.10.0.
Maintenance Version
Maintenance Versions contain important bug fix releases, but otherwise offer the same features and services as the major version they iterate. They are carefully altered to fix specific issues without affecting or modifying any other part of the product.
Upgrading to a new Maintenance Version of your current Major Version (for example, v5.10.0 to v5.10.1) is a trivial exercise and extensive testing of your Verj.io Application is usually not required.
Maintenance Versions iterate the Verj.io Version’s maintenance component, for example v5.10.0 -> v5.10.1.
Verj.io Version Releases
Releases for all Verj.io products are created at the same time with matching Verj.io Versions.
New Verj.io Studio, Verj.io On-Premises and Verj.io Gateway releases are immediately made available for download along with comprehensive release notes describing any changes, including any bug fixes.
Rarely, there may be a re-release of a given version, to resolve some critical issue. This release will have a different build timestamp to the one being replaced but will in all other ways be identical (fixes to the issues withstanding). Usually, these releases only happen if we become aware of serious issues immediately after release.
Verj.io Cloud
Verj.io Version Releases include new Verj.io Application Containers. Existing Verj.io Service Plans must be upgraded to use the latest Verj.io Application Containers and are upgraded in a timely fashion depending on the type of release.
Landmark Series Release
Verj.io Service Plans will be upgraded within 60 days after the release a new Landmark Series was made publicly available. At the time of the public release, you will be notified of the target upgrade date.
The Verj.io Studio will be available for download to allow you to locally test your Verj.io Applications with the new Verj.io Version prior to the Verj.io Service Plan upgrade.
Verj.io Service Plan upgrades may be delayed if an issue is discovered in the release that results in a corrective release being made available before the Verj.io Service Plans have been upgraded. Depending on the nature of the issue, the upgrade may be delayed for a further 21 days from the date the corrective release was made publicly available. You will be notified of any changes to the upgrade date for your Verj.io Service Plans.
Major Version Release
Verj.io Service Plans will be upgraded within 30 days after the release a new Major Version was made publicly available. At the time of the public release, you will be notified of the target upgrade date.
The Verj.io Studio will be available for download to allow you to locally test your Verj.io Applications with the new Verj.io Version prior to the Verj.io Service Plan upgrade.
Verj.io Service Plan upgrades may be delayed if an issue is discovered in the release that results in a corrective release being made available before the Verj.io Service Plans have been upgraded. Depending on the nature of the issue, the upgrade may be delayed for a further 21 days from the date the corrective release was made publicly available. You will be notified of any changes to the upgrade date for your Verj.io Service Plans.
Maintenance Version Release
Verj.io Service Plans will be upgraded within 7 days after the release a new Maintenance Version was made publicly available.