We recommend that our customers perform their own QA testing with the public beta release to verify and take advantage of new functionality and best practices. At a minimum, your QA team should install and test the beta Pulsar application to verify operations continuity. During this beta testing period, please send us your feedback about any issues or concerns. Once the QA test feedback period ends, we re-run our own testing and QA processes before publishing the new Pulsar application for general release on all app stores.

In rare circumstances we may need to publish a point release of the Pulsar app to fix a critical bug in production. These point releases go through our same internal testing and QA processes, but are immediately published to the appropriate app stores in order to quickly remedy a situation for affected customers.

Since Pulsar is a mobile application, your end users are ultimately in control of the release they download to their devices. This is a general release management problem when it comes to mobile applications by the very nature of how they are distributed through various application stores. Some of our customers use MDM (Mobile Device Management) software to control the application distribution. With MDM’s help you can enforce strict control on which Pulsar version you distribute to your users after the release went through your rigorous internal testing.