Releasing v1.8.0, removing v1.8.1 + 1.8 + 1.7

[lecoqlibre]

!!! WARNING: possible breaking changes !!!

As discussed before we are going to release a clean 1.8.0 version of the ontology. This will be the latest version until the release of the 1.9.0 (which should be released soon).

THIS RELEASE WILL BE PUBLISHED ON 2023/10/02.

This release won't contain the taxonomies anymore and it will drop the old static website (https://static.datafoodconsortium.org). Is some people still using some files on the static website? Can we remove it safely?

Also, once we release the 1.8.0 we plan to drop the 1.8.1, 1.8 and 1.7 versions. Can we remove them safely?

The businessAPI folder will also be deleted. Ok for you @simonLouvet? These should be used from the dedicated repo now.

@Alcoz @RaggedStaff @simonLouvet

[simonLouvet]

ok @lecoqlibre

[mkllnk]

it will drop the old static website (https://static.datafoodconsortium.org/). Is some people still using some files on the static website? Can we remove it safely?

We're currently using taxonomies which point to the old website because the Connector doesn't work with the new taxonomies yet. But I don't think that the removal would break anything.

Why do you want to take the website down? Can't you keep it for old applications which haven't updated yet? It could be useful to have a transition time before deleting old things.

once we release the 1.8.0 we plan to drop the 1.8.1, 1.8 and 1.7 versions. Can we remove them safely?

It's generally very bad practice to revoke releases. Why do you have to remove them? Wouldn't it be good to have a historic record? If the new version is super-seeding all the old one then you could choose a version number that's newer than the old ones, like 1.8.2. 🤷

[lecoqlibre]

We're currently using taxonomies which point to the old website because the Connector doesn't work with the new taxonomies yet. But I don't think that the removal would break anything.

OK and the connector should be updated before the release but indeed you are free to load the taxonomy files you want so it should not break anything.

Why do you want to take the website down? Can't you keep it for old applications which haven't updated yet? It could be useful to have a transition time before deleting old things

The static website is subject to deletion from a long time now and removing it would make things clearer. The resources it was listing are now/will be available on our GitHub home page.

It's generally very bad practice to revoke releases. Why do you have to remove them? Wouldn't it be good to have a historic record? If the new version is super-seeding all the old one then you could choose a version number that's newer than the old ones, like 1.8.2. 🤷

These releases are invalid (number and content) and should be deleted. They have just been released to fix things when it was time.

[RaggedStaff]

Why do you want to take the website down? Can't you keep it for old applications which haven't updated yet? It could be useful to have a transition time before deleting old things.

I think there's been a misunderstanding here. I don't think we're talking about actually switching off static.datafoodconsortium.org, just updating the references (some of which already point to the github releases folder).

There are updates to the Taxonomy files coming soon, which will remove all references to static. @lecoqlibre - do we need to align the release of the Ontology updates with the Taxonomy updates? 🤔

It's generally very bad practice to revoke releases. Why do you have to remove them? Wouldn't it be good to have a historic record? If the new version is super-seeding all the old one then you could choose a version number that's newer than the old ones, like 1.8.2. 🤷

I appreciate this isn't an ideal strategy. We're moving to semantic versioning, with agreed release procedures (feedback welcomed), for all Ontology changes. these releases don't align with the new versioning strategy and are likely to cause confusion/unnecessary errors. The history will always be available in the github repos.

@lecoqlibre @Alcoz - I'm wondering if v1.9.0 might be better placed as v2.0.0, what do you think?

[lecoqlibre]

I think there's been a misunderstanding here. I don't think we're talking about actually switching off static.datafoodconsortium.org, just updating the references (some of which already point to the github releases folder).

References will be updated but the static website will be removed also as we all agreed several months ago.

There are updates to the Taxonomy files coming soon, which will remove all references to static. @lecoqlibre - do we need to align the release of the Ontology updates with the Taxonomy updates?

Sure, it would be nice to release the proper taxonomies for use with the ontology at the same time we release the ontology. If we don't, the new ontology won't be usable out-of-the-box until we do. If you talk about version numbers, ontology and taxonomies are 2 different items living their own life thus there is not need to align them.

I appreciate this isn't an ideal strategy. We're moving to semantic versioning, with agreed release procedures (feedback welcomed), for all Ontology changes. these releases don't align with the new versioning strategy and are likely to cause confusion/unnecessary errors. The history will always be available in the github repos.

We are in the process of cleaning the repo. The mentioned releases (1.7, 1.8, 1.8.1) have been temporary released and are full of errors. They were waiting for us to clean everything and to make a consistent history. For me, they should not be considered in the history, right?.

I'm wondering if v1.9.0 might be better placed as v2.0.0, what do you think?

According to semantic versioning:

• MAJOR version when you make incompatible API changes
• MINOR version when you add functionality in a backward compatible manner
• PATCH version when you make backward compatible bug fixes

Are we making incompatible API changes in the 1.9.0 version? Or maybe even in the 1.8.0?