@@ -31,7 +31,18 @@ The current branching strategy is for **beta development and release of v7**.
* [ ] Run `generate_changelog.py`
* [ ] Tag, release, etc
* [ ] Check that the MR in the openflexure.org repository is approved and ready to merge after successful release
* [ ] Check that the MR for any website wording changes in the `openflexure.org` repository is approved and ready to merge after successful release
*The next section is best done on a video call with at least one other team member to ensure better understanding across the core team.*
* [ ] Run `generate_changelog.py`
* [ ] Go to *Releases* page on GitLab and select New Release
* [ ] Create a new Tag Name in the format `vX.Y.Z` or `vX.Y.Z-(alpha|beta)A`
* [ ] **Important!** Enter a simple description into the `create tag` dialog, or GitLab only creates a lightweight tag. `Release for vX.Y.Z-(alpha|beta)A` is minimal and can be used. Check it is targeted at the correct branch, and save the tag.
* [ ] Copy in the relevant section from the `CHANGELOG`
* [ ] Enter the URL to the where the documentation will sit on the build server under the title "Docs".
* [ ] Create the release (This will create the tag)
### Immediate post release checks and communication
