Best practices for upgrading Resco software
|Warning||Work in progress! We are in the process in updating the information on this page. Subject to change.|
This document should provide ideas and best practices when it comes to updating the Resco solution and its parts.
The first practice that we highly recommend is to use the sandbox environment for introducing any kind of changes. This does not only apply to the Resco suite. Always test the new versions of Resco software and any other software or hardware that you want to use.
Resco is only able to fix any reported issues in the Resco software (Woodford, Resco mobile apps, Resco Cloud, Houston, Inspections, ...) by updating the appropriate part of the solution. Given the rapid improvements and changes in the mobile device world, Resco has committed to 4 major releases each year, where new features and major improvements are introduced:
- Spring release (usually March)
- Summer release (usually June)
- Autumn release (usually September)
- Winter release (usually December)
In between these major releases, there can be a bugfix release introduced, in case of an issue that can only be improved by changing the solution or its part.
At least two weeks before a major version release, we start beta testing. We provide a beta version of the Woodford solution and mobile applications, available (and Beta2 one week later) for test. This test is designed to test the current customizations with new, planned release, and also to test the new features (especially important for those, who requested the functionality, to check if it fits their needs).
This Beta testing allows us to check with you, our customers, and partners, if there are any issues with the planned release on existing (various, complex) customizations soon enough, to perform changes for the final release, and avoid any unwanted issues at launch of the new version.