We regularly release new versions of our software, including quality improvements and new features. Here we explain the procedure we adhere to when rolling out software updates to customers.
This article is only applicable to customers making use of our 'software-as-a-service' (SaaS) model. For on-premise customers, different conditions apply.
Maintenance windows
Updates always take place on thursdays after 17:00 (CET/CEST), unless (temporary) deviating agreements have been made. This is our “Maintenance Window”, during which standard downtime may be expected. Changes to an environment involve updates due to new releases from Roseman Labs, but also changes in the configuration of the deployment (e.g., increase RAM, CPU, etc.).
When a new release is rolled out, either for crandas or for the platform, its release notes will be made available in the changelog on the crandas documentation or the help center respectively. For the platform, release notes are provided in Dutch as well. If a release contains many new features, or when it involves breaking changes of which users should be aware, the maintenance will be announced via email at least a week in advance.
Release channels
Roseman Labs supports two types of release channels: the 'latest' channel and the 'quarterly' channel. In the latest channel, a version will be rolled out to the customer as soon as it has been released (provided the conditions in section 'maintenance windows'). In the 'quarterly' channel, the customer will have one maintenance window each three months, in which they receive the latest version that has been released at that point in time. A customer can choose for either of these release channels. If desired, releases may be tested on a dedicated acceptance environment.
Version support
The crandas version that runs in the analytics environment of the analyst should always be on par with the version that runs on their remote environment (engine). When they should update depends on the release channel they are subscribed to.
Note: As part of each collaboration, we will agree on a service level agreement (SLA). When this article deviates from the SLA, the SLA will be leading.