Creating a release

Step

Plan
- Create milestone
- Select bugs to target
- Pick freeze date, after which no big changes occur until release
- Pick release date (and update milestone)
- Start writing release notes
Communicate to forum
- Timeline
- Invite translators (and make sure Crowdin is up-to-date - should be automatic, but if not: crowdin upload -b master --tree)
- Invite testers
- Ask if there are important things to include in the release notes
Merge, test, check, double check
At release date
- Merge any new translations in the source tree (crowdin pull commit changes but not new files)
- Make sure tests are ok (GitHub actions)
- Finalise release notes and update CHANGELOG.md (conventional-changelog -p angular -i CHANGELOG.md -s)
- Bump VERSION (use X.Y.Z version number)
- Commit with message "Bumped new version: X.Y.Z"
- Optionally, tag vX.Y.Z-rc[0-9]* if you would like to test the release candidate with Docker.
- Tag vX.Y.Z
- Update tag latest-release (for download links)
- Bump VERSION file to vX.Y.99, commit with message "continue development after release" to master.
- Check tags latest-release, X.Y.Z and X.Y are building on Docker
Announce
- foodsoft forum
- on matrix channel
- foodcoops.net website
- on other places, if you like
update the release procedure wiki page
Celebrate!