Skip to content

Latest commit

 

History

History
48 lines (33 loc) · 2.36 KB

RELEASE.md

File metadata and controls

48 lines (33 loc) · 2.36 KB
Raw

Major / Minor Release

Below are the steps needed to do a release. But rather than doing them by hand, you can run this script:

https://github.com/eclipse/che-devfile-registry/blob/master/make-release.sh

HOWEVER, because the master branch is protected from commits, the above script will not be able to commit an update to the VERSION file. Instead it must produce a PR.

remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: At least 1 approving review is required by reviewers with write access.
To github.com:eclipse/che-devfile-registry
 ! [remote rejected] master -> master (protected branch hook declined)
  • create a branch for the release e.g. 7.8.x
  • provide a PR with bumping the VERSION file to the 7.8.x branch
  • Release Build Status CI is triggered based on the changes in the release branch (not 7.8.x).

In order to trigger the CI once the PR is merged to the 7.8.x one needs to:

 git fetch origin 7.8.x:7.8.x
 git checkout 7.8.x
 git branch release -f 
 git push origin release -f

CI will build an image from the release branch and push it to quay.io e.g quay.io/eclipse/che-devfile-registry:7.8.0

The last thing is the tag 7.8.0 creation from the 7.8.x branch

git checkout 7.8.x
git tag 7.8.0
git push origin 7.8.0

After the release, the VERSION file should be bumped in the master branch, e.g. to 7.9.0-SNAPSHOT.

Service / Bugfix Release

The release process is the same as for the Major / Minor one, but the values passed to the make-release.sh script will differ so that work is done in the existing 7.7.x branch.

./make-release.sh --repo [email protected]:eclipse/che-devfile-registry --version 7.7.1 --trigger-release