Skip to content

Conversation

glpatcern
Copy link
Member

@glpatcern glpatcern commented Sep 10, 2025

We are introducing a new API to fix a mis-named API for OCM: the new "Incoming OCM" serves as a one-on-one replacement of the so-called "Core OCM" API, which is deprecated and will be removed in a later change.

This is a breaking change because of the introduction of a new API, and I seek the approval of all stakeholders: @rhafer @kobergj please tag who may comment on this.

cc @rawe0 @jessegeens @diocas

This is a one-on-one replacement of the so-called "Core OCM" API,
which is now deprecated and will be removed in a later change.
@glpatcern glpatcern changed the title Introduced the Incoming OCM API. Fixes #150. Introduced the Incoming OCM API Sep 10, 2025
@glpatcern glpatcern linked an issue Sep 10, 2025 that may be closed by this pull request
@rhafer
Copy link

rhafer commented Sep 24, 2025

@butonic @dragotin any thoughts about this? This is basically "just" a rename.

@kobergj
Copy link
Contributor

kobergj commented Sep 24, 2025

I think the new naming makes sense. @2403905 what do you think? Does it fit?

@glpatcern
Copy link
Member Author

Thanks for your comments, and glad to see all of you showing interest. Indeed it's a "simple rename" even if it requires a code change in Reva.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

How do ocm/core and sharing/collaboration relate?

3 participants