...
When you have a parent issue and subtasks, they should appear in the changelog in a nested form, like so:```
Info | ||
---|---|---|
| ||
* ERM-904 Update tooling and framework * ERM-906 Update licenses to Grails 4 * ERM-909 Update docker image to Java 11 |
...
- Commit changelog changes and push up to github
- If doing a bugfix, first increment version number by 1 on patch, ie 3.0.0 -> 3.0.1, then raise a PR and merge to long life release branch, ie release_v3.0.x.
- DO NOT MERGE BACK TO MASTER
- Go to your branch on github, select "releases" on the left hand side and "draft new release". Make sure the Target is set to your release branch, and the tag is of the form `vx.y.z`, ie `v3.0.0` or `v5.2.1` etc. Give the release a name, `Version 3.0.0` and fill in the explanation with the changes you already made to the changelog, along with the header:
...
Info | ||
---|---|---|
| ||
## 3.0.0 2020-10-14 * ERM-1046 Non-phrase searching support for licenses * ERM-967 Add "Note" to Organisation link in Licenses * ERM-904 Update tooling and framework * ERM-906 Update licenses to Grails 4 * ERM-909 Update docker image to Java 11 * ERM-828 Add support for "Alternative name" for licenses * ERM-975 Licenses: Use /organizations/ instead of /organizations-storage/ * ERM-742 Custom properties: Backend validation not working |
...
for example. Then click "publish release".
...
- Once that's done, double check the release has made it here:
- [mod-agreements](https://hub.docker.com/r/folioorg/mod-agreements/tags)
- [mod-licenses](https://hub.docker.com/r/folioorg/mod-licenses/tags)
- [mod-service-interaction](https://hub.docker.com/r/folioorg/mod-service-interaction/tags?page=1&ordering=last_updated)
- [mod-serials-management](https://hub.docker.com/r/folioorg/mod-serials-management/tags)
- Announce the release on slack channel `#releases`, with message
...
Info | ||
---|---|---|
| ||
mod-licenses v3.0.0 released https://github.com/folio-org/mod-licenses/releases/tag/v3.0.0 |
with a link to the github tagged release page.
...