Release process

For maintainers, steps for the release process:

Update the corresponding section in the changelog with bullet points reflecting major features merged into master since the previous release
Make sure you have the latest master state pulled to your local copy
Tag the release with the next release number which also be found at the top of the readme as it always reflects the current version being worked on on the master branch , e.g. 0.04: git tag 5.35
Push the tag to upstream: git push origin 5.35
The build pipeline should start automatically once the tag is pushed including the steps build and publish-release
Once completed successfully, the release is published on the releases page
Edit the latest release
Copy-pate the change log section of the respective version into the description
Un-check Set as pre-release
Check Set as the latest release
Click Update release
Notify any other channels, e.g. the pigs in the stall, about the latest release:
1. New post in thread
```
<insert version here> released: <direct link to published version>

Changelog:
<paste changelog here>
```
2. Update the OP title by bumping the version number in it
3. Update the OP post by extending it accordingly (see previous entries)
Bump the version number at the top of the readme and add a new empty section in the changelog with the new version number as title. Commit changes and push to master branch
Continue developing and merging PRs until you decide its time for another release