1. There can be multiple pull requests to the fellowship runtime repository. The fellowship members are required to approve these pull requests.

2. When it is time to create a new release, someone needs to open a new pull request. The bare minimum that this pull request needs to do is to alter the CHANGELOG file (this will then trigger the release process once merged to master). This pull request could also include other changes like:

   • New weights plus the description of the machine that was used to generate them (which is actually part of the weight file, so this should be enough).
   • Adding migrations and ensuring they are correct

3. When the pull request for a new version is ready, it needs to be approved by the fellowship members again.

4. The pull request hits master and the release logic triggers a new release. This release can then be proposed on chain.