Currently we offer manual, guided updates, which are conducted by a member of our development team. When Matrix Requirements finalises a new version, here is what happens:
When a major version is released:
An email is sent to all the admin users of Matrix, explaining that there is a new version and what are the new features (this last happened June 29th, 2021 for version 2.3). This email includes a date for the upgrade, a possibility to test the new version in a cloned instance and a possibility to opt out.
If a customer decides to opt-out, the upgrade doesn't take place. The customer can come back to us at a later date to ask for the upgrade.
For the customers who do not ask to opt-out, the upgrade takes place at the given date.
An email is sent after the upgrade took place to explain the status.
When a minor patch version is released:
Minor patch updates are currently not communicated proactively, as they contain mostly minor changes and improvements but no major features.
Minor patch updates are recommended if customers reach out to us to report an issue and we consider the update to be beneficial for their situation.
When considering an update we ask customers to provide a timeframe that would be convenient for them to conduct the update to avoid disruptions as the instance will not be reachable for a few minutes during the update process.
Relevant for both updates:
As part of the regular backup process, all your data is saved in redundant servers every hour. If anything goes wrong during the upgrade, we have the ability to restore your instance with the previous version.