mirror of
https://github.com/openfoodfoundation/openfoodnetwork
synced 2026-01-27 21:06:49 +00:00
03c35aaeaf
The release tag was pre-filled with `v` which was meant to help you type the release number. But I observed multiple times now that an actual tag named `v` was created. That tag can be quite annoying in the history. So let's remove this tiny help to avoid mistakes. I personally use `script/release/tag` which pre-fills the next tag already. [skip ci]
2.6 KiB
2.6 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Release task | Track the process of a new release | Release v |
1. Preparation on Thursday
- Merge pull requests in the Ready To Go column
- Include translations:
script/release/update_locales - Increment version number:
git push upstream HEAD:refs/tags/vX.Y.Z- Major: if server changes are required (eg. provision with ofn-install)
- Minor: larger change that is irreversible (eg. migration deleting data)
- Patch: all others. Shortcut:
script/release/tag
- Draft new release. Look at previous releases for inspiration.
- Select new release tag
- Generate release notes and check to ensure all items are arranged in the right category.
- Notify #instance-managers of user-facing 👀, API ⚠️ and experimental 🚧 changes.
2. Testing
- Move this issue to Test Ready.
- Notify
@testersin #testing. - Test build: Deploy to Staging with release tag.
3. Finish on Tuesday
- Publish and notify #global-community (this is automatically posted with a plugin)
- Deploy the new release to all managed instances.
Command line instructions
cd ofn-install git pull ansible-playbook --limit all_prod --extra-vars "git_version=vX.Y.Z" playbooks/deploy.yml
- Notify #instance-managers:
@instance_managers The new release has been deployed.
- Create issue for next release and confirm with next release manager in #core-devs.
The full process is described at https://github.com/openfoodfoundation/openfoodnetwork/wiki/Releasing.