Release Notes Overview¶
Egeria is a large and active project with teams advancing its function on multiple fronts. Our work is split across multiple git repositories that supply components on different release schedules. Therefore, we aim to provide an update on our activities and releases in our monthly newsletter.
The roadmap for Egeria describes the end vision for Egeria and our current status.
One way you can help us is to feedback on your experiences, both good and bad. We would love to hear from you!
If you discover an issue in the release you are using, we recommend first upgrading to the latest available release. If this does not resolve the problem, please raise a new GitHub issue .
You can also follow our discussions by joining us on Slack .
Core Egeria Function¶
The Core Egeria technology is located in the egeria.git repository. It provides the OMAG Server Platform, java clients for the OMAG Servers that run on the OMAG Server Platform along with the Conformance Test Suite (CTS).
The project aims to produce a new release of Core Egeria about once every 6 weeks. Each release includes new features and fixes to existing function. This is also an opportunity to update the levels of our dependencies to reduce vulnerabilities.
The table below shows the planned dates for future releases. The branch date is the date that a copy of the main branch is taken. This copy is the candidate code for the release. We then run tests on this copy and release to maven central once any issues have been resolved. Any fixes that are necessary are made to the main branch and then back-ported to the release branch. It typically takes a week to go from making the release branch to the new release going to maven central.
|Release||Branch date||Release Date||Core theme|
|4.2||17th July 2023||20th July 2023||Runtime optimization|
|4.3||4th September 2023||New assemblies|
|4.4||23rd October 2023||Apache Atlas connector(s)|
|4.5||4th December 2023||OpenLineage update|
|4.6||22nd January 2024|
|4.7||11th March 2024|
|4.8||20th May 2024|
|4.9||1st July 2024|
|4.10||2nd September 2024|
The team aims to provide complete backward compatibility for all components that are officially released1.
If backwards compatible changes are not possible, it will be called out explicitly in the release notes with an explanation on how to upgrade.
Each release will also upgrade the level of its dependencies to ensure Egeria is running with all the latest security patches. We therefore recommend that you keep moving forward with us to get the best Egeria experience possible.
Our main branch is currently taking code for all future releases. Many of the features are large and the teams integrate code for partial function as soon as it is stable and has no impact on released function. So you will see support for much more function than is officially released. This way you can monitor and feedback on future items as they are developed.
Raise an issue or comment below