Release Notes
elDoc versions overview:
- v5.11.1
- v5.11.0
- v5.10.0
- v5.9.2
- v5.9.1
- v5.9.0
- v5.8.9
- v5.8.8
- v5.8.7
- v5.8.6
- v5.8.5
- v5.8.4
- v5.8.3
- v5.8.2
- v5.8.1
- v5.8.0
- v5.7.4
- v5.7.3
- v5.7.2
- v5.7.1
- v5.7.0
- v5.6.1
- v5.6.0
- v5.5.3
- v5.5.2
- v5.5.1
- v5.5.0
- v5.4.6
- v5.4.5
- v5.4.4
- v5.4.3
- v5.4.2
- v5.4.1
- v5.4.0
- v5.3.8
- v5.3.7
- v5.3.6
- v5.3.5
- v5.3.4
- v5.3.3
- v5.3.2
- v5.3.1
- v5.3.0
- v5.2.0
- v5.1.2
- v5.1.1
- v5.1.0
- v5.0.12
- v5.0.11
- v5.0.10
- v5.0.9
- v5.0.8
- v5.0.7
- v5.0.6
- v5.0.5
- v5.0.3
- v5.0.2
- v5.0.1
- v5.0.0
Breaking changes
As a general rule, backward compatibility is maintained between minor versions (e.g., 5.x to 5.y), allowing upgrades without changes to configuration files or reconfiguration of IDP or BPM components.
If backward-incompatible modifications are introduced in a minor release (e.g., 5.0 to 5.1), such changes are explicitly documented in the Release Notes. Prior to any upgrade, the relevant Release Notes should be reviewed to identify potential breaking changes.
Upgrades between major versions (e.g., 3.x to 5.y) may include breaking changes, and Release Notes for all intermediate versions should be consulted when transitioning from older major versions of the elDoc system.
General rule: a valid and recent database backup must be in place before any upgrade is performed.
elDoc Product Lifecycle and End-of-Life Policy
elDoc is provided with a minimum 5-year software lifecycle, including support and maintenance. New releases are generally delivered with backward compatibility and automated upgrade mechanisms, enabling smooth transitions within the same major version.
| Version | First Release | End Of Life |
|---|---|---|
| elDoc v5.x | May 2020 | TBD* |
* not early than Q4 2025
Actively Maintained Versions
To align with established industry practice and to ensure the highest level of security, stability, and maintainability, support is limited to Actively Maintained Versions.
The term actively maintained versions refers to releases that are part of the current maintenance stream and receive ongoing updates, security fixes, and feature improvements. Within the elDoc platform, the latest available minor version of the current major release (for example: 5.10.x when versions such as 5.8.x and 5.9.x are also present) is designated as the actively maintained version.
Earlier minor releases remain supported only insofar as an automated, forward-compatible upgrade path to the actively maintained version is available. Maintenance efforts are concentrated on the latest minor release, and no separate maintenance branches are provided for superseded minor releases.
This model ensures a consistent support lifecycle and allows all installations to remain current through the built-in automated upgrade mechanism.
Version Support Matrix
| Major Version | Minor Version(s) | Support Status | Notes |
|---|---|---|---|
| 5.x | 5.11.x (latest) | Actively Maintained | Receives updates, fixes, security patches, and enhancements. |
| 5.10.x | Supported (upgrade path available) | No independent maintenance branch; auto-upgrade to 5.11.x supported. | |
| 5.9.x | Supported (upgrade path available) | No independent maintenance branch; auto-upgrade to 5.11.x supported. | |
| Older 5.x versions | Supported (upgrade path available) | Must rely on automatic upgrade to the latest 5.x release. | |
| 3.x | All | End of Life | Upgrade to the latest major release is required; no updates or maintenance provided. |
Legend
Actively Maintained
Receives full maintenance: updates, fixes, security patches, and enhancements.Supported (upgrade path available)
Not maintained independently; support provided through a direct, automated upgrade path to the latest minor release.Limited Support / End of Maintenance
No new updates; assistance limited to guidance on upgrading.- LTS
For installations unable to transition to the actively maintained version, an LTS arrangement may be established. LTS provides component upgrades and critical security fixes for out-of-stream versions on an individually agreed basis. End of Life
No maintenance, no fixes; upgrade required.
Exception Policy for Long-Term Support (LTS)
In exceptional circumstances where an installation cannot be upgraded to the latest actively maintained version, Long-Term Support (LTS) may be provided on an individual basis. LTS coverage may include essential component updates, critical security fixes, and high-priority maintenance required to ensure continued operational stability.
LTS availability is determined case-by-case and may require a dedicated support agreement, as older versions fall outside the standard maintenance stream.
This exception mechanism ensures that installations with operational constraints can remain secure and stable, while the primary maintenance focus continues to follow the standard support lifecycle based on the latest minor release.
Last modified: November 13, 2025