Versionning scheme and publication automation

[ymorin-orange]

What:

• We currently have no versionning scheme for the release of the various components.
• Components are not automatically published to the corresponding "registries" (crates.io, PyPi, Mavenc central)

---

Expected:

1. There is a clear policy about the versionning scheme. Shall we have:
   • a single versionning for all components and release everything at once?
   • a versionning per language, and release all components in that language at once?
   • a versionning for the SDK as a whole and release a single SDK in all languages at once? If so, what about the various components (e.g. in python)?
   • a versionning per component in each language?
2. Once the versionning policy has been established, how do we enforce it:
   • github workflows to publish?
   • how to detect that comething has to be relased:
     • tag fomatting scheme?
     • metadata in tag commit log?
   • where to publish the JSON schemas?

[nbuffon]

1. We all agree that one version for all is not suitable
2. No version change in functional branches
3. Version changes have to be made in dedicated branches
4. When merging into master, check the diff to identify if any version has changed.
   If any, build and publish the new package at the new version; and a new git tag is created language.module-version
5. If at publish a package at this version already exists, the pipeline job must fail
6. Example are not published
7. Semantic tags (created manually): YYYYmmdd.HHMM-purpose
   E.g. 20241120.1212-Demo-5GLab
8. Version should follow the X.Y.Z form where X is major, Y minor, and Z fix (see https://semver.org/)
9. Create a new webpage (gh-pages)
10. Rust packages are published on crates.io; and documentation on docs.rs
11. Python packages are published on pypy.org; and documentation on readthedocs.com
12. Java packages are published on ?

[nbuffon]

• Document the release process (previous comment content) in a file at the repository root (e.g. RELEASE-PROCESS.md)
• Create dedicated issues by language