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:
-
Rapid channel releases contain the newest GA release features and fixes and are deployed to sandbox[1] environments.
-
Regular channel releases contain established GA release features and fixes and are deployed to development, UAT[2], staging, and production environments.
Optionally, you can defer releases from the regular channel to your production environment to let you test and validate regular channel releases.
Release versions
Ping Identity gives each release in each channel a unique release version. The release version is numeric (for example, 15158.7) and increases with each successive release. A greater release version includes the changes from lesser release versions.
The release version 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
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.
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].
Track regular channel releases
You can track regular channel releases in these ways:
-
-
Subscribe to email notifications:
-
Scroll down to Documentation Digests.
-
Check the Advanced Identity Cloud Regular Channel Changelog checkbox.
Release deferral
|
Advanced Identity Cloud limited availability feature
Release deferral is a limited availability feature. It is also an opt-in feature. Contact your Ping Identity representative if you are interested. |
Ping Identity lets you defer regular channel releases to your production tenant environments for up to seven days. This allows you to test and validate new regular channel releases in your lower environments (development, UAT[2], and staging) using your most up-to-date configuration.
You can trigger the deployment of the regular channel release to your production environment at any time during the seven-day deferral period by running a promotion from your staging environment to your production environment. Otherwise, at the end of the seven-day deferral period, the regular channel release is automatically deployed to your production environment.
In the rare event that Ping Identity applies a hotfix to the regular channel release while you are testing it in the lower environments, the seven-day deferral period in your production environment is not extended. This ensures that Ping Identity can apply security updates quickly and effectively without impacting the cadence of scheduled regular channel releases.
You can use the release information from your production environment to track the seven-day deferral period.
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.