Hyperscience manages the upgrade process for SaaS instances. Your Hyperscience representative will let you know when a new version of the application is available and work with you to coordinate the upgrade.
To learn more about Hyperscience upgrades, in general, review our Upgrade Process Overview. While the article describes the upgrade process for on-premise / private cloud instances of Hyperscience, it helps you understand the work Hyperscience will complete on your behalf and the types of model-training tasks you will be asked to assist with.
Upgrade processes
The upgrade process differs based on the type of upgrade being completed.
Major version upgrades
When upgrading from one major version of the Hyperscience application to another (e.g., from v31.x.x to v32.x.x), Hyperscience works with you to complete the following steps:
Your Hyperscience representative lets you know that a new version is available and schedules the upgrade of your pre-production environments. They will request access to these environments, which you can revoke when the upgrade is completed.
Hyperscience upgrades the pre-production environments and attaches the trainer for the new version to your production environment.
Your Hyperscience representative works in partnership with you to train new models in the production environment and perform any necessary testing of the models in pre-production. They will request access to your production environment, which you can revoke when the upgrade is complete.
After the models have been successfully trained, your Hyperscience representative contacts you to schedule the upgrade of your production environment.
Hyperscience completes the upgrade in your production environment.
Patch version upgrades
After releasing a major version, Hyperscience works on fixes and updates for that version and releases them in patch versions (e.g., v31.0.1 would be a patch version of v31).
Patch version upgrades require less effort to complete than major version upgrades because no new models need to be trained.
When a new patch version becomes available, Hyperscience completes the following steps:
Your Hyperscience representative lets you know that a patch version is available, and they will tell you the maintenance window in which they will upgrade your pre-production and production environments. The windows for pre-production and production will likely be about one week apart. If upgrades during the proposed windows would be problematic for your business, work with your Hyperscience representative to create a revised upgrade schedule.
Hyperscience upgrades your pre-production environments during the pre-production maintenance window.
Hyperscience upgrades your production environment during the production maintenance window.
Minor version upgrades
Hyperscience may release minor versions of its application as new features become available (e.g., v31.1.x would be a minor version of v31).
Hyperscience performs minor version upgrades of SaaS instances on a case-by-case basis, depending on the features included in those versions. Your Hyperscience representative will work with you to determine if the minor version would benefit your business. If you decide to complete the upgrade, Hyperscience will follow the process for either major version upgrades or patch version upgrades, depending on the features included in the minor version.