- Update local branches (fetch/pull)
- develop
- master
- Bump version
- Create new issue in VIVO JIRA project (https://jira.lnd.bz/projects/VIVO) called "Release/Hotfix x.x.xx"
- Create new branch issue/VIVO-xxx from master branch (git checkout -b issue/VIVO-xxx)
- Bump version in file VERSION, update text in README.md, commit this change to branch issue/VIVO-xxx and push it
- Create pull-request from issue/VIVO-xxx to preview and merge it
- Create release (hotfix)
- git checkout master
- git flow release/hotfix start x.y.z
- merge all branches to release/hotfix branch (git merge issue/VIVO-xxx, last merge should be the issue with version bump)
- git flow release/hotfix finish x.y.z
- Push
- master
- develop
- tags
- Control git graph (e.g. on bitbucket)
- if merge commits look O.K. (compare two last releases/hotfixes)
- if tags have been pushed
- Update dependencies to Vivo on projects vivodemo, vivoproject, if neccessary and test new release
- Create Confluence page with issue list like Vivo 2.2.2 change log or Vivo 2.2.3
- Create/update release in VIVO JIRA project (tag all isues, fill in release date)
- Update change log on Vivo web - http://vivo.lundegaard.eu/cs/vivo-cms/change-log/
- Update Vivo documentation for developers and editors - VIVO, Vivo Documentation
- Let people know about new version wherever you can
...