Review GitHub release process

[tschaffter]

Should we rely on the branch main to create released? Shall we create release branches?

[boyleconnor]

What about doing releases with tags?

[thomasyu888]

+1 for tags

[tschaffter]

I am currently using tags for releases. I create a tag that points to a commit on the branch develop whenever needed.

Here I would like to open the discussion to the complete release process. Part of the discussion could involve:

• Shall we use GitFlow
• Currently a tag is created by one person. It would be neat if this action could be set to require approval like we do before PR merging.
• Do we want to adopt semantic release?
• Currently we have one version for all the API (schemas repo). Here we version the ecosystem and all the components that have the same API version should work together. Do we agree with this approach?

Instead of starting writing a long ticket, we can discuss this in our next meeting. Then we need to write down a protocol and implement it by configuring the GitHub repositories and CI/CD workflow. It's important that this release process account for us opening the development of this project to the community. For example the development workflow should account for external users using Forking Workflow.

[tschaffter]

Linked to #27