Skip to content

Latest commit

 

History

History
17 lines (15 loc) · 1.07 KB

DEVELOPMENT.md

File metadata and controls

17 lines (15 loc) · 1.07 KB
Raw

Development

Release Checklist

  • create a release branch called release/v<version> like release/v1.1.0
  • rename every occurrence of the old version, say 1.0.0 or 1.1.0-SNAPSHOT into the new version, say 1.1.0
  • rename every occurrence of old Docker images like ghcr.io/medizininformatik-initiative/feasibility-backend:1.0.0 into the new image, say ghcr.io/medizininformatik-initiative/feasibility-backend:1.1.0
  • update the CHANGELOG based on the milestone
  • create a commit with the title Release v<version>
  • create a PR from the release branch into the main branch
  • merge that PR (after proper review)
  • create and push a tag called v<version> like v1.1.0 on the main branch at the merge commit
  • create a new branch called new-dev on top of the release branch
  • change the version in the POM to the next SNAPSHOT version which usually increments the minor version, e.g. 1.2.0-SNAPSHOT
  • merge the new-dev branch back into develop
  • create release notes on GitHub
  • delete the release-branch and the new-dev branch after they have been successfully merged