Release Notes

The most important new functions are described on this page.

Changes within the BPC version are documented at Changelog.

Explanation of versioning

Versions of the BPC are regularly released with different version numbers. A version number consists of three parts: major.minor.patch.

A change to the major version number(e.g. 4.0) indicates that the release contains significant changes to the software. For example, APIs have been changed or removed, major changes have been made to the user interface or major features have been removed or added.
The change to the minor version number(e.g. 4*.3*) may contain new features or changes to existing features or the removal of features. Changes may also occur for supported platforms (e.g. databases, operating systems, Git versions).
The change of the patch version number(e.g. 4.3*.1*) may contain bug fixes, stability and performance improvements. Minor changes to existing features may be delivered, but these do not include new features or critical changes.

Breaking changes are usually intended to close potential security vulnerabilities and can therefore occur in all releases. However, the aim is still to place these changes in major releases.
Breaking changes are highlighted in Changelog.

4.2

Better use of resources in the BPC cluster

If the BPC is operated in a cluster, replications are now distributed between the individual Karaf nodes. An attempt is made to distribute the individual replications evenly across all available Karaf nodes.