Serraview Release Management
Continuous Delivery
Our Release Management approach for Serraview and Engage is to use Continuous Delivery. We will release upgrades to your Serraview instance by using continuous delivery. Also, learn about the Engage mobile app delivery.
Another term for Continuous Delivery is Evergreen. This is where the software is kept up-to-date with automatic updates, typically without any customer intervention.
What you gain
- Frequent small releases to allow for incremental change.
- Reduces risks of bugs being shipped to production as regressions are captured early by automated tests.
- Building the release is easy as all integration issues have been solved early.
- Deployment is automated and requires minimal user intervention.
Also, there is information on the Product Upgrades and Maintenance Windows.
Plan - Develop - Test
Our product and development team plan, develop, and test each release. As the development and quality assurance is completed, established checkpoints must be signed-off before the product is considered ready for release.
Now let us focus on the part that matters to you ....
Upgrade
The development and release process will include several stages:
- Alpha - The product release is available for internal testing.
- Beta - The product is available for testing and feedback by a larger group of users. This is a first look at the new features and enhancements.
- Early Access - The product is available to a chosen selection of customers.
- General Availability - The product is released to production and ready for all customers.
Upgrade to UAT Environment
We aim to release every 2 to 3 weeks depending on the number of features in the upgrade. Upgrades will be released to your UAT Environment; this is where we will complete our final checks to ensure the latest release is a success.
Release Notes
When we are ready to upgrade your UAT Environment, we will complete the release notes in the product overview article , see What's new in Serraview. The product overview content will be gathered from our product and development team and will be published close to the time of the upgrade. This is to ensure the accuracy of the content.
Upgrade from UAT to Production Environment
After the successful upgrade of the UAT Environment, then after 1 week we will upgrade the Production Environment.
Product Documentation
Detailed product documentation will be made available in the Help Center and the product overview article will include relevant content, screenshots, and links when the documentation is completed .
Adhoc Fix
If a critical issue is found, we will release an Adhoc Fix we will test this internally before it is released to the UAT environment. The fix is verified in the UAT environment and then the Production environment is upgraded.
Operate
As you use Serraview in your business you will be supported by the Serraview Product Team and the Serraview Support team. Additionaly, in Serraview you will see the Help icon which contains the quick link to the Knowledge Center and the Product Support panel where you can access the release notes in the What's New section, Knowledge Center, Suggest a Feature, and Submit a Support Request. Learn more in Product Support.
App Release Cycle
Our Release Management approach for the Engage App is to use Continuous Delivery to the App Store for Android and iOS devices.
Push to Alpha Channel
We aim to release as needed, depending on the number of features in the upgrade. Upgrades will be released to the Alpha Channel for testing and we will complete our final checks to make sure the latest release is a success.
App Store Approval and release to App Store
After the successful upgrade of the Alpha Channel and with the App Store approval, the app will be released to the App Store.
Adhoc Fix
If a critical issue is found, we will release an Adhoc Fix; we will test this internally before it is released. The fix is verified in the Alpha Channel, and then with the App Store Approval, the app will be released to the App Store.
The Microsoft Intune app release is a couple of versions behind due to the technical limitations of incorporating SDK in Engage.