Chore: Reset version number to wip following r2.1

[eric-murray]

What type of PR is this?

• subproject management

What this PR does / why we need it:

Version numbers need to be reset to wip following r2.1

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

None

Changelog input

 release-note
 - Chore: Reset version number to wip following r2.1

Additional documentation

None

[GillesInnov35]

@eric-murray , I'm sorry but could you explain why changing to vwip the release candidate v0.2-rc version before M4 and the public version ?
does it follow release management process ?
Thanks
Gilles

[eric-murray]

Because there might be other changes made between 0.2.0-rc.1 and 0.2.0. What we definitely want to avoid is that someone finds a version "0.2.0-rc.1" in main that is different to what is in r2.1. And the safest way to avoid that possibility is to revert the version numbers in main back to wip immediately after a tag has been created.

We had that problem early in the OGW Market Champions project, and had to reference a specific Github commit to ensure there was no ambiguity in which version of the API we were all implementing, because there were multiple commits in the repository that all had the same version number.

[GillesInnov35]

Thanks Eric for your precisions.