Release Management

New releases can be created by Egeria maintainers that have the appropriate access on Azure Pipelines.

Releases are published to Bintray where they are GPG signed and distributed to Maven Central.

Overall Release Policy

Obtaining releases / artifacts

## Release process summary

Release Process in detail

1. Agreement of overall schedule

2. Tracking remaining issues (stability)

3. Create branch

4. Update master version & cleanup notes

5. Test and Merge

4. Update branch version

5. Create a release in Azure dev pipelines

6. Finalizing the release

Release Process Troubleshooting

The Linux Foundation maintains a Knowledge Base (KB) of articles on possible issues that may arise during the release process:

If the KB articles are not able to fix the problem, please open a ticket with Linux Foundation support


License: CC BY 4.0, Copyright Contributors to the ODPi Egeria project.