Open Source Release Policy
Bloomreach applies the following policy to releasing the code and built artifacts of Bloomreach Experience Manager.
This decision allows us to focus on enhancing the stability, security, and performance of our enterprise software, while continuing to provide valuable updates to the open source community. It will also enable us to further invest in the innovation and features that deliver the greatest impact to your organization’s success.
Thank you for your understanding and continued trust in our software. If you have any questions or need further clarification, please don't hesitate to reach out to your Account Manager or to the Channel Management team.
Open Source Releases
Bloomreach provides Bloomreach Experience Manager as open source to the community under the open source Apache Software License 2.0. Developers can attain the source by simply cloning the public community git repositories from https://github.com/bloomreach/brxm.
Furthermore, for each community release, Bloomreach also provides the built artifacts through the Maven repository hosted at https://maven.bloomreach.com.
Release tags and artifacts only
Bloomreach only provides the git trees for the release tags of Bloomreach Experience Manager. Code changes which are under development, for major, minor or maintenance releases, are not synchronized nor updated in the public community git repositories. Existing outdated/stale branches must not be used, they will be removed in the near future.
Bloomreach only shares its Bloomreach Experience Manager released source code with the community, along with the corresponding git history. Sharing the released source code allows Bloomreach to provide reliable support for community developers, customers and partners, and to process their contributions and feedback efficiently. Likewise, Bloomreach provides built Maven artifacts for released versions only. Snapshot builds representing ongoing development are not available publicly.
Early release access for Customers and Partners
In accordance with its security policy, Bloomreach may provide customers and partners with early access to new releases, for example when a new release provides not-yet-disclosed security fixes. Bloomreach does so in order to allow its customers to update their production environments before the vulnerability is disclosed and the fix is released to the community.