From d47128e355e2d49e96ef9abcd6ca18657ccfa918 Mon Sep 17 00:00:00 2001 From: David Cook Date: Fri, 10 Nov 2023 12:14:52 +1100 Subject: [PATCH] Describe how to choose version number Thanks Maikel for summarising this: https://community.openfoodnetwork.org/t/release-numbering/105/6 --- .github/ISSUE_TEMPLATE/release.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release.md b/.github/ISSUE_TEMPLATE/release.md index 2412f5e7c3..8d4f82b4a6 100644 --- a/.github/ISSUE_TEMPLATE/release.md +++ b/.github/ISSUE_TEMPLATE/release.md @@ -11,9 +11,10 @@ assignees: '' - [ ] Merge pull requests in the [Ready To Go] column - [ ] Include translations: `script/release/udpate_locales` -- [ ] Create a tag: - - `script/release/tag` will auto increment patch version, otherwise - - `git push upstream HEAD:refs/tags/vX.Y.Z` +- [ ] 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.