Review release process

[RachL]

Current release process is unclear for the community.

We've decided during tech meeting we need to review the process again.

First step is for Garethe and Maxime to quickly chat about it and hopefully reach a proposal.

[RaggedStaff]

I think there are a couple of things here:

1. There aren't clear release processes for the Connector/UML model.
   i. This seems to have resulted in a lot of changes sitting in dev branches & not getting merged.
   ii. There is a risk there - it would be better/clearer if changes were merged once ready.
2. There is no way to map the dependencies between releases, see datafoodconsoritium/ontology#172 but perhaps we should discuss this more generally across the whole standard ?

[RaggedStaff]

The Ontology team have agreed to use dc:requires to specific a minimum version for each Taxon in the Ontology file, see #174.

@lecoqlibre proposes adding custom fields/properties to the UML Model to indicate which (minimum?) Ontology version to use.

[lecoqlibre]

On 2025/04/15: we will have both:

• custom fields/properties to the UML Model to indicate which (minimum?) Ontology version to use;
• keep the SUPPORTED.md file to list what is supported from the used ontology version.

[RaggedStaff]

@lecoqlibre Could you link a PR to close this?

Will be part of the same PR as #18

[lecoqlibre]

We could in the connector.uml root file:

• add a comment about the model
• or apply a custom stereotype on the model to define a new property like ontology version.

Otherwise we could just precise the expected ontology version in the CHANGELOG file?

@RaggedStaff

[RaggedStaff]

I think both the custom property ontology-version and noting in CHANGELOG.md would be best.

That way we have a machine readable & human readable version.