Release Process and Product Roadmap

New release candidates are first introduced to our clients via their stage environments. This is after the release has gone through two Alpha cycles. The decision to move the release into the live environment is discussed with our clients based on several factors:

1. The urgency of the release
2. The length of time it’s been error-free in Beta
3. The desirability of the new features

After a few months of error free beta testing, the new release will be moved into production with out much fanfare. However, with the introduction of our new formal release process, clients will play a more pivotal role in deciding when to move a release into production.

Unfortunately, after a release is in production there may be unforeseen issues introduced. These issues usually show up within a day or two and can be dealt with in various ways depending on severity:

1. Rollback to the previous release
2. Soft-patch where corrections can be made without the need for a new release
3. Hard-patch – a new version of the release with required patches

The Roadmap is client driven as requests for modules and general wish-list requirements are communicated to our team.