This documents the standard procedure for packaging a new release of farmOS 2.x. It is used as a checklist by the maintainers to ensure that all the necessary steps are taken.
(A similar document was maintained for farmOS 1.x here: Release procedure - farmOS.org)
- Confirm:
- Drupal core and pinned modules are up-to-date
- 2.x branch build is successful
- Release:
- Create “farmOS [version]” commit (eg: farmOS 2.0.0-beta2 · farmOS/farmOS@2b76832 · GitHub)
- Update CHANGELOG.md with new version and release date
- Tag new version
- Push 2.x and tag to origins
- Wait for GitHub Actions to create release
- Create release node in drupal.org (eg: https://www.drupal.org/project/farm/releases/2.0.0-beta2)
- Copy text from github release
- Link to GitHub release for tarball
- Create “farmOS [version]” commit (eg: farmOS 2.0.0-beta2 · farmOS/farmOS@2b76832 · GitHub)
- Announce:
- Chat
- Forum (eg: farmOS 2.0.0-beta2 has been released)
- OpenCollective (eg: farmOS 2.0.0-beta2 has been released - Open Collective)
- Mastodon (automated via farmOS-microblog)