Exago Logo
Search
Generic filters
Exact matches only

Understanding Exago Releases

Exago releases will follow a regular schedule designed to maximize throughput of features and bugfixes and maintain stability between releases. This graphic illustrates how the Exago version number corresponds to the releases and fixes.

Anatomy of an ExagoBI version number


Feature Releases

Several times a year, a new version of Exago with an enhanced feature set will be released.

Example: v2020.2.5.124

The 2 following 2020 indicates the second feature set release of 2020.

Bugfix Releases

Monthly, bugfix releases will be made to all applicable supported feature set releases.

Example: v2020.2.5.124

The 5 indicates the fifth bugfix release of the second feature set of 2020.

Release Timeline

The Exago team always makes a best effort to include enhancements and fixes for issues as early as possible. In order to determine priority for the inclusion of such changes, the team takes into account several factors including the urgency of the client’s issue, overall impact of the change to the product, and Exago’s own development timeline.

Early-Access Releases

By request, Exago may provide early access to the feature set version currently in development before it is released as a fully developed and tested “stable” version. To know whether or not a release is an early-access version, examine the last number (build number) in the version string.  Any build number less than 100 indicates an early-access release.

Example: v2020.2.5.124

The last numbers, beyond the second decimal are less than 100, which indicates an early-access release

v2016.2.5.124 indicates a GA release.

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents