PingOne Advanced Identity Cloud

Release process

Ping Identity continuously provides general availability (GA) releases to PingOne Advanced Identity Cloud to introduce new features, fix known issues, and address security issues.

GA releases are delivered through two channels:

  • A rapid channel release contains the newest GA release features and fixes and is deployed to your sandbox[1] environments.

  • A regular channel release contains established GA release features and fixes and is initially deployed to your development, UAT[2], and staging environments to let you test and validate it. It’s then released to your production environment after a deferral period of up to 7 days. Learn more about the deferral period in Release deferral.

Release versions

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:

  • 15158 is the major version. It increments with each new general availability (GA) release.

  • 2 is the minor version. It increments with each update to that GA release.

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.

Rapid channel

The rapid channel delivers a continuous stream of the newest features and fixes as soon as they are ready for GA release.

  • For sandbox customers: Releases deploy automatically to your sandbox[1] environments, allowing you to test and evaluate new features against your custom implementation.

  • Rapid channel changelog: Whether you have sandbox[1] environments or not, following the rapid channel changelog gives you advance visibility into new features, fixes, and improvements that are likely to be included in an upcoming regular channel release. This lets you prepare your team and plan updates before changes reach your non-sandbox environments.

The rapid channel 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 becomes eligible for release to the regular channel.

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

Track rapid channel releases

You can track rapid channel releases in these ways:

Regular channel

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]. The regular release is initially deployed to your development, UAT[2], and staging environments to let you test and validate it. It’s then released to your production environment after a deferral period of up to 7 days.

Track regular channel versions

To get release information from each of your environments, you can use the Release information API or the Tenant settings page:

  • Track the current release version.

  • Track the next scheduled regular channel release date and time (for the Tenant Settings page, this is displayed in a banner at the top of the page).

Track regular channel releases

You can track regular channel releases in these ways:

Hotfixes

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.

1. A sandbox environment is an add-on capability.
2. A user acceptance testing (UAT) environment is an add-on capability.
3. Exact release schedules depend on multiple factors and are subject to change.