Release Policy
All Camunda components follow the release policy outlined below.
For additional version-specific release policy information see:
- Camunda 7 Release Policy
- Camunda 8 Release Policy (including SaaS provisioning)
Versioning
Components of Camunda follow the Semantic Versioning standard, which defines a version number using the MAJOR.MINOR.PATCH pattern.
- MAJOR version can make incompatible changes to public API.
- MINOR version can add functionality in a backward-compatible manner.
- PATCH version can make backward-compatible bug fixes.
Standard Support Period
Camunda provides a standard support period of 18 months for their Enterprise customers. Therefore, Camunda supports at least the last three released minor versions with patch releases. Patch releases are offered on a best-effort basis for the currently supported versions.
Release Cadence
The Camunda team strives to release at least:
- Every six months (in April and October): a new minor version release
- Every month: patch releases for all supported versions
- In between minor versions: alpha releases to preview the upcoming minor version
The Camunda team strives to release versions on the second Tuesday of the respective month.
What does "End of Maintenance" mean?
End of maintenance means that Camunda will not perform any maintenance or release any bug fixes and patch releases related to the mentioned version after the specified date. In case you are planning to migrate to a more recent version of Camunda, check our Camunda 7 Update & Migration Guide or our Camunda 8 Update Guide.
Please let us know if you have any concerns or if you need help migrating to a new version.
Why does Camunda change Supported Environments?
Camunda is committed to delivering improvements and bug fixes as fast as possible. We are also committed to providing world class support for our software running in different environments. However, as new versions of databases, web browsers, etc, are released, the cost of supporting multiple environments grows exponentially, making it harder to provide the level of support our customers have come to expect from us. Therefore, we no longer support environments marked as end-of-life by the vendor, or very old versions that are no longer widely used.
