Release process

Ping Identity assigns each release a unique version number, which helps track what’s included and when it’s released.

Instead of separate version numbering for the rapid and regular channels, both increment the same sequence. Version numbers are cumulative. A higher number includes all earlier updates.

Each version number follows a major.minor format. For example, in version 15158.2:

The version number is displayed in your tenant environments and in each published changelog entry to let you track which features are in your tenant environments.

If you have a sandbox^[1] environment, a continuous stream of the newest features and fixes are deployed there as soon as they are ready for GA release. This lets you test and evaluate GA releases to make sure they are compatible with your Advanced Identity Cloud implementation. It also lets Ping Identity qualify and establish GA releases through cumulative usage and soak testing, typically over a two-week period. When a GA release has been established, it is allocated to the regular channel and deployed into your development, UAT^[2], staging, and production environments.

For early access to documentation about features in the rapid channel, learn more in Rapid channel features.

Only established GA releases are deployed to your development, UAT^[2], staging, and production environments. Typically, two weeks' worth of GA releases in the rapid channel are rolled up into one release to the regular channel 2–4 weeks later^[3].

In general, Ping Identity applies critical hotfixes to both the rapid and regular channels.

On occasion, Ping Identity can apply hotfixes as necessary to the rapid channel only. These hotfixes will be released to the regular channel at a later time.