Creating a release

Steps

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 mailing-list foodsoft-dev@
- 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 (run script/crowdin-pull, commit changes but not new files)
- Make sure tests are ok (GitHub actions)
- Finalise release notes and updateCHANGELOG.md
- Bump VERSION (use X.Y.Z version number)
- Commit with message "Bumped new version: X.Y.Z"
- 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
- on mailing-list foodsoft-announce@
- on Twitter
- on sourceforge news
- on other places, if you like
Celebrate!