Please note this policy has been superseded by a new version: ForgeRock End of Service Life (EOSL) Policy and EOSL Dates
This article is provided for reference purposes only.
|Major version||May introduce major new functionality, remove redundant functionality or deprecate functionality that will be removed at a future date. Consolidates bug fixes from previous updates. Possible architectural changes requiring a review of deployment topology; for example: Access Management 7.0.0|
|Minor version||May introduce new modified features and enhancements alongside bug fixes; for example: Access Management 6.5.0|
|Maintenance release||May introduce minor improvements alongside bug fixes. These are full releases, and designed as drop-in updates on-top of the most recent major or minor release that should require no configuration changes; for example: Access Management 6.5.3 or Directory Services 6.5.4|
|Patch release||Only includes bug fixes. These are full releases, and designed as drop-in updates on-top of the most recent major or minor release that requires no configuration changes; for example: Access Management 18.104.22.168 or Identity Management 22.214.171.124|
|Date of Release||The date of release is the date when the initial major release of a ForgeRock product is made publicly available. The EOSL dates for all current releases of ForgeRock Software are listed in the [Superseded] Checking your product versions are supported document.|
This policy applies to users of ForgeRock software with a current, valid subscription.
- Version numbers are of the form major.minor.maintenance-release.patch-release.
Support schedule for Major versions:
- All software will be fully supported for 3 years from the date of release.
- For one additional year, critical fixes and critical and high security fixes will be made available as individual patches as required.
- Critical and high security fixes advisory notices will therefore include software versions up to 4 years from the date of release.
- All support ceases 4 years from the date of release.
Minor, maintenance releases, patch releases and patches
- ForgeRock will typically release a minor release in the year directly following the preceding major release; for example: Access Management 6.5.0 after Access Management 6.0.0.
- Maintenance releases are always built on top of the latest major or minor release; for example: After Access Management 6.5.0 is released, all subsequent maintenance releases on that major version will follow from the minor release as Access Management 6.5.x and not from the original major release.
- Maintenance releases will be issued periodically, and it is strongly recommended that customers update to the latest maintenance release as soon as possible.
- Patch releases will be issued more frequently than maintenance releases and contain fewer fixes. It is strongly recommended that customers update to the latest patch release as soon as possible.
- Minor, maintenance and patch releases provide mid-life fixes and/or enhancements; these releases do not extend the EOSL dates for the product.
- All customers are encouraged to use the latest versions of the ForgeRock products.
- As subscriptions are not tied to a specific version, there is no additional software licensing cost for upgrading!
EOSL policy for embedded components
- ForgeRock software such as Access Management can contain embedded versions of other ForgeRock software products such as Directory Services. When a ForgeRock software product has been embedded and distributed as part of another ForgeRock software release, the EOSL timeline that applies to the top-level software release shall also apply to all and any embedded versions of ForgeRock software. This statement only applies to embedded software and does not affect the EOSL timeline of the products when they are distributed as standalone releases.