Skip to content

Release process

New releases can be created by Egeria maintainers that have the appropriate access on each GitHub repository.

Releases are published to

Maven Central Quay.io Docker.io

Overall release policy

  • Aim to release approximately every month
  • Typically, target end of month for external availability
  • Will only release an update between releases in exceptional circumstances
  • Preserves backwards compatibility as much as possible
  • Try and maintain a regular heartbeat: even if completion of some features continues in a subsequent release
  • master / main kept open for new code features
  • When the core Egeria is released, we have found it useful to create releases of other Egeria repositories (connector and user interface repositories) using the same version numbers as core Egeria.
  • Egeria charts are produced for each release of core Egeria; these charts include compatible user interface and connector content.

Releases for different repositories

The Egeria project is split across different git repositories, so that each repository can be built independently and can have its own community. Here are the release processes for Egeria repositories:

Git repository Description Update process
https://github.com/odpi/egeria Egeria core Egeria core Release process
https://github.com/odpi/egeria-react-ui Egeria React UI Egeria React UI Release process
https://github.com/odpi/egeria-charts Egeria charts Egeria charts Release process
https://github.com/odpi/egeria-docs Release guide Egeria Update Release Guide process
https://github.com/odpi/egeria-connector-xtdb XTDB connector XTDB connector release process
TODO Other Egeria Git repositories TODO
Back to top