Software Release Process
TAP Workflow Automation Software Release Process
We maintain a defined process for software releases based on current industry best practices. The process provides a predictable, controlled, and efficient software release cycle, positively impacting operational excellence and most importantly customer satisfaction.
Multi-Environment Release Process
We manage the release of new workflow automation features and enhancements across multiple environments. This is considered a best practice for managing software releases in a controlled and systematic manner. This strategy involves four distinct software environments or stages through which code and changes are moved before reaching end-users in production.
The purpose of this strategy is to minimize the risk of introducing errors or issues into the production environment and to ensure that new features and updates are thoroughly tested before reaching users.
Environments
- Development
Multiple internal environments where Mitratech software and quality assurance (QA) engineers and teams work on code changes, new features, and bug fixes. - UAT
The environment used by Mitratech, customers, and partners to review changes and perform quality assurance activities in consideration for release. We encourage everyone to do the majority of their testing in UAT. - Staging
The environment used by Mitratech to test automated deployment capabilities and processes. This is also a secondary environment where external parties may perform additional testing and validation. - Production
The "live" environment where end-users employ their workflows to automate business processes. It's where the software runs in the real world, serving clients and making workflow.
Software Versions
Mitratech classifies software versions into three groups. Because of the scope, each release warrants a different quality assurance strategy and, therefore, may progress through the environments at different rates.
- Minor releases are smaller, incremental updates to the software. These updates often include multiple bug fixes, minor feature additions, or performance improvements.
- Major releases are significant and substantial updates to the software. It usually includes major new features, enhancements, or changes that can have a substantial impact on the user experience.
- Patch releases are tightly focused changes that resolve one or more software defects.
Environment |
Minor Release Duration Before Promotion |
Major Release Duration Before Promotion |
Data Refresh |
|
Development |
n/a |
n/a |
n/a |
|
UAT |
Scope dependent (3 days minimum)
|
Ten business days* |
With each major release |
|
Staging |
Five business days |
Five business days |
n/a |
|
Production |
n/a |
n/a |
n/a |
When appropriate these target timeframes may be adjusted to best handle environmental conditions. We will provide as much advanced notice as possible. If you have any questions please reach out to customer support.