-
Notifications
You must be signed in to change notification settings - Fork 62
Release procedure
Marcin Maciaszczyk edited this page Jun 3, 2019
·
4 revisions
- Test the application manually at least for basic functionality.
- Create a new tag and release.
- Use semver to pick version number.
- Minor and major releases should be created from
master
branch. - Patch releases should be created from
release/x
branch.
- Verify that images were uploaded to the registry.
- After creating new major or minor release create a new release branch (i.e.
release/1.2
). - Update the version in the kubermatic/kubermatic repo.
- If the release is only nice to have (not urgent) and should not cause new release of the whole application mark it in the pull request.