EDC - Stable Management API

eclipse-tractusx / sig-release

https://eclipse-tractusx.github.io/sig-release

Apache License 2.0

8 stars 8 forks source link

EDC - Stable Management API #757

Open lgblaumeiser opened 2 months ago

lgblaumeiser commented 2 months ago

Description

In the past almost with each version (also patch versions) breaking API changes were introduced in the EDC. This hurts a lot and creates a lot of efforts while adopting patched or new versions of the EDC into the Use-Cases of Catena-X as also for EDC as a Service providers and companies that need to link/integrate the EDC with 3th party software. Therefore breaking change should be handled correctly with semantic versioning.

Requestor: @florianrusch-zf

Impact

Impact would be more stability for components that depend on the management api.

Additional information

[ ] I'm willing to contribute to this feature

lgblaumeiser commented 2 months ago

Two upstream decisions records build the basis for the discussion:

EDC deprecation policy: https://github.com/eclipse-edc/docs/tree/main/developer/decision-records/2024-05-27-maturity-levels-deprecation-policy
API Versioning: https://github.com/eclipse-edc/docs/tree/main/developer/decision-records/2024-05-20-api-versioning-2

lgblaumeiser commented 2 months ago

This is a feedback I have received from multiple sides. The comment from @florianrusch-zf above is only one of them.

In general, my impression is, that there are misunderstandings in what we talk about, so the proposal from todays discussion was, that we start on this item by doing a small workshop in which we clarify pains and expectations on the one hand side and existing measures and processes on the other hand side to identify options for improvements.

stephanbcbauer commented 1 month ago

Presented in the DRAFT Feature Freeze -> Committer is available