As this project shall have shared ownership between Camunda BPM and Zeebe in the future, let's create some guidelines to make collaboration easy and where certain changes can be made independently of the other team.
- Define that we strictly stick to semantic versioning.
- Define what a breaking change is from the Camunda BPM perspective (i.e. what would require a new major version of feel-scala). In the future we can add the Zeebe perspective and if we adhere to both, we can keep everyone happy.
- Define which changes must always be agreed on between the teams (e.g. all breaking changes in the above sense)
- This should be documented in the repository and every maintainer should be aware of it (implementor and reviewer)