Release: New version of odo

Releasing a new version

Making artifacts for a new release is automated within RedHat's internal CI servers.

1. Create a PR to update the version. Using the helper script scripts/bump-version.sh update the version in the following files:

• pkg/version/version.go
• Dockerfile.rhel
• scripts/rpm-prepare.sh

2. Merge the above PR.
3. Once the PR is merged create and push the new git tag for the version.
4. Create a new release using the GitHub site (this must be a proper release and NOT a draft).
5. Update the release description (changelog) on GitHub. For this, you will need a personal access token from GitHub (to overcome potential rate limit issues). If not already done, generate a GitHub personal access token, and note the token. You don't need to select any special scope. Run the script below to get the baseline template of release changelog:

export GITHUB_TOKEN="<personal_access_token_generated_before>"
./scripts/changelog-script.sh ${PREVIOUS_VERSION} ${NEW_VERSION}

6. Update the Homebrew package:
7. Check commit id for the released tag git show-ref v0.0.1
8. Create a PR to update :tag and :revision in the odo.rb file in kadel/homebrew-odo.
9. Create a PR and update the file build/VERSION with the latest version number.
10. Create a blog post! Follow the template.md file and push it to the website; learn how to push to the website here.
11. After the blog post, ideally the CHANGELOG in the release should be the same as the blog post. This is an example of a good release changelog: https://github.com/redhat-developer/odo/releases/tag/v2.0.0
12. Add the built site (including the blog post) to the release with site.tar.gz using the bundling the site for releases guide.