...
Upgrade / Update Process
New in 3.9.12.When a new update becomes available, our automated process installs a copy of your live server (after anonymizing some of the user information for privacy reasons) on one our internal update staging servers designed specifically for update testing purposes. It then applies the software update and runs a complete system health check, which executes over 21,000 automated tests. Any Improvements in both our processes and products means that Dual Code can now offer its clients zero-touch updates. Zero-touch updates mean that clients no longer need to schedule the update of their systems via our Help Desk nor verify the update on their staging server before approving the upgrade of their live environment.
Our release process now requires the successful execution of over 21,000 automated tests against all areas of the system before an update becomes generally available. And that's not all! We then further verify each and every client installation by applying the update to a copy of their live environment and then running a complete system health check. Any reported failure will be inspected by one of our application specialists for resolution. Once 100% of the tests pass. If no failures are reported, the system will automatically schedule the update of both your production live and staging server and send you a notification via email and using the system's built-in notification tool. Note that starting in 3.9.12, the update of the notify all System Administrators.
The system will automatically schedule the production and staging server are scheduled to take place be updated at the same time as since you are no longer required to review and/or approve the update of your production server. That being said, if it is your preference to verify the new functionality on a staging server prior to updating your production server, you may accelerate the update of your staging serverupdates. This will eliminate pain points for organizations as well as delays, and in turn reduce your exposure to cyber attacks. Organizations who prefer to assign resources to manually verify the update on their staging server prior to updating their live environment can continue to do so by leveraging tools built-in the learning environment to re-schedule the date and time of their update.
Depending on the nature of the update, you administrators also have the option to reschedule and/or skip the update on your production server as wellan update. Skipping an update is only possible if the update is not mandatory (e.g. if it doesn't contain critical security issues AND if your any high priority security fixes and if the system is no more than 2 releases versions behind).
This fully automated process ensures that keeping your site up-to-date is simple, easy and safe! It requires zero-touch from you and your team. And it is definitely much safer than the risk associated with not upgrading your learning environment!
Release Schedule
...