For customers who are unable to upgrade to the latest major release series (e.g. 5.x), Mersive will provide important software fixes and improvements to customers who are still on the previous major release series (e.g. 4.x) through updates to the terminal release in that series. This allows customers who are still on the previous release series that are unable to upgrade to the latest release series (e.g. due to the customer’s internal policies, etc.) to still get access to important and critical bug fixes such as security updates, while limiting the number of software versions that Mersive is actively releasing.
Active software series: The latest major software series that Mersive is actively developing and releasing software updates for. For example, if Mersive is actively developing and releasing software updates for the 5.x software series, then 5.x is the latest major software series.
Inactive software series: Any previous major software series that Mersive is no longer actively developing and releasing software updates for but is still being supported and has not reached its end-of-life. For example, if Mersive moves to the next major release series (such as 5.x), then the previously released 4.x software series becomes an inactive software series.
Terminal Release Policy
- A terminal release is any released software version that is designated by Mersive as the terminal release for a software series.
- Mersive can designate zero or multiple terminal releases within a major software series. Mersive reserves the right to add or remove terminal releases as needed.
- Mersive may designate a release as a terminal release if it is the last minor software version released in an inactive software series. For example, if the last software release within the previous software series was 4.6, then 4.6 may be designated as the terminal release for the 4.x software series.
- Mersive will continue to provide software fixes and improvements to the terminal releases of an inactive software series until that series reaches its end-of-life, at which time Mersive will no longer support it.
- Pods with active subscriptions who are unable to update to the active major release series (e.g. due to the customer’s internal policies, etc.) can update to a terminal release and any subsequent patch releases in order to get important software fixes and improvements.
- Updating to a terminal release version is not required; however, Mersive strongly recommends that Pods be updated to benefit from the latest fixes.
- Terminal releases are not supported for End-of-Life (EOL’d) versions of Solstice software and hardware.
- Solstice administrators will be able to see any available software versions the Pod is entitled to, including terminal releases, and update Pods to that software version using Solstice Cloud or the Solstice Dashboard.
If you have any questions at all, please contact Mersive Support at email@example.com or open a support ticket in our Support Portal for further assistance.