Skip to main content
Eptura Knowledge Center

Eptura Workplace Release Management

  1. Last updated
  2. Save as PDF

Continuous Delivery

Our Release Management approach for Eptura Workplace and Mobile Apps is to use Continuous Delivery. We release upgrades to your Eptura Workplace instance by using continuous delivery into your Production Environment. Also, learn about the 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 the risk 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.

releasemgt1.png

Plan - Develop - Test

Our product and development team plan, develop, and test each release. As 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 ....

releasemgt2.png

Upgrade

releasemgt3.png

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.

Production Environment

We aim to release every 3 weeks.

Release Notes

When we are ready to upgrade your Production environment, we will complete the release notes and these will be published in the What’s new in Eptura Workplace. The release notes will only be published close to the time of the upgrade, this is to ensure the accuracy of the content.

Knowledge Center Documentation

The detailed product documentation will be published in the Eptura Workplace Knowledge Center after the release to production. Also, the release notes will be updated with links to the relevant article(s) 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 Production environment. 

Operate

As you use Eptura Workplace in your business, you will be supported by our Eptura Knowledge Center and the Support team. 

App Release Cycle

Our Release Management approach for the Eptura Workplace Apps (such as Eptura Hummingbird, iOffice Asset, iOffice Service Request, iOffice Mail, and iOffice Visitor) is to use Continuous Delivery to the App Store for Android and iOS devices.

releasemgt4.png

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.