[SofaGraphComponent] Fix a typo in the warning emited by the APIVersion component and add missing allowed versions.

[jnbrunet]

Using this in your scene:

<APIVersion level="21.06" />

gave (before this PR):

[WARNING] [APIVersion(APIVersion)] The provided level '21.06' is now valid.

and now gives (with this PR);

[WARNING] [APIVersion(APIVersion)] The provided level '21.06' is not valid. Allowed versions are [17.06, 17.12, 18.06, 18.12, 19.06, 19.12, 20.06, 20.12, 20.12.99].

---

By submitting this pull request, I acknowledge that
I have read, understand, and agree SOFA Developer Certificate of Origin (DCO).

---

Reviewers will merge this pull-request only if

• it builds with SUCCESS for all platforms on the CI.
• it does not generate new warnings.
• it does not generate new unit test failures.
• it does not generate new scene test failures.
• it does not break API compatibility.
• it is more than 1 week old (or has fast-merge label).

[alxbilger]

I am just concerned about what happens if the provided level is invalid. The rest of my comments are just ultra-minor suggestions.

[alxbilger]

What happens next if the version is invalid? Wouldn't it be better to set a default value (e.g. SOFA_VERSION_STR)?

[jnbrunet]

Nothing will happen. The purpose of this component is not super clear, but if I understood correctly (maybe @hugtalbot or @guparan could correct me if I'm wrong):

• Adding <APIVersion level="21.06" /> in your scene is simply used to specify to the user that this scene was written using SOFA v21.06.

Hence, the message emitted here warns the user author of the scene that he probably didn't meant v21.06 since this version does not exists yet (the largest API version is 20.12.99).

Now, we could probably talk about this version number thing at the next dev meeting (cc @hugtalbot for the agenda!) . I often see in other projects the master branch having the version number of the next upcoming release. For example, for the next release, it could look like this:

1. master branch has version 21.06
2. Close to the release, a v21.06 branch is created and an alpha or beta binary release is created from this branch
3. master branch version is updated to 21.12 (even if 21.06 is not released yet)

Using this, setting <APIVersion level="21.06" /> in scene files of the master branch would make sense.

[guparan]

Now, we could probably talk about this version number thing at the next dev meeting (cc @hugtalbot for the agenda!) . I often see in other projects the master branch having the version number of the next upcoming release. For example, for the next release, it could look like this:

1. `master` branch has version 21.06

2. Close to the release, a `v21.06` branch is created and an alpha or beta binary release is created from this branch

3. `master` branch version is updated to 21.12 (even if 21.06 is not released yet)

Using this, setting <APIVersion level="21.06" /> in scene files of the master branch would make sense.

You are right, the project version was wrong. I used this opportunity to fix it 👍

[hugtalbot]

Let's get this merged, but I still do not understand the big picture of this component. It is not spread over SOFA and there is no policy about it.