Open Source Release Policy

Bloomreach Content follows the release policy outlined below for open source code and built artifacts.

Info:
Starting June 2023, Bloomreach applies a 24-month delay between enterprise software releases and their corresponding open source versions.
This change allows Bloomreach to prioritize stability, security, and performance improvements for enterprise customers, while continuing to support the open source community.
For questions or clarification, contact your Account Manager or the Channel Management team.

Open Source Releases

Bloomreach Content is available to the community under the Apache Software License 2.0.
You can access the source code by cloning the public repository at https://github.com/bloomreach/brxm.

For each community release, Bloomreach also publishes built artifacts to the Maven repository at https://maven.bloomreach.com.

Release Tags and Artifacts

Bloomreach provides only the git trees for release tags of Bloomreach Content.
Code under development—whether for major, minor, or maintenance releases—is not synchronized or updated in the public git repositories.
Do not use outdated or stale branches; these branches may be removed in the future.

Bloomreach shares only the released source code and its corresponding git history with the community.
This approach enables Bloomreach to support community developers, customers, and partners, and to process contributions and feedback efficiently.
Built Maven artifacts are available only for released versions.
Snapshot builds and ongoing development artifacts are not published publicly.

Early Release Access for Customers and Partners

According to the security policy, Bloomreach may provide customers and partners with early access to new releases, such as those containing undisclosed security fixes.
This early access allows customers to update production environments before public disclosure of vulnerabilities and before fixes are released to the community.