Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Update local branches (fetch/pull)
    1. develop
    2. master
  2. Bump version
    1. Create new issue in VIVO project (https://jira.lnd.bz/projects/VIVO) called "Release/Hotfix x.x.xx"
    2. Create new branch issue/VIVO-xxx from master branch (git checkout -b issue/VIVO-xxx)
    3. Bump version in file VERSION, update text in README.md, commit this change to branch issue/VIVO-xxx and push it
    4. Create pull-request from issue/VIVO-xxx to preview and merge it
  3. Create release (hotfix)
    1. git flow release/hotfix start x.y.z
    2. merge all branches to release/hotfix branch (git merge issue/VIVO-xxx, last merge should be the issue with version bump)
    3. git flow release/hotfix finish x.y.z
  4. Push
    1. master
    2. develop
    3. tags
  5. Control git graph (e.g. on bitbucket)
    1. if merge commits look O.K. (compare two last releases/hotfixes)
    2. if tags have been pushed
  6. Update dependencies to Vivo on projects vivodemovivoproject, if neccessary and test new release
  7. Create Confluence page with issue list like Vivo 2.2.2 change log or Vivo 2.2.3
  8. Update dependencies to Vivo on projects vivodemo, vivoproject (actually not necessary, in composer.json 2.2.*) and test new releaseUpdate change log on Vivo web - http://vivo.lundegaard.eu/cs/vivo-cms/change-log/
  9. Update Vivo documentation for developers and editors - VIVO, Vivo Documentation
  10. Let people know about new version wherever you can (wink)

...