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 a new GitHub release, by choosing the new tag name. Doing so will create and push the new Git tag for the version.
4. 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:

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

5. This generates a ./release-changelog.md file in the repo. You will need to include the content of this file in the description of the GitHub release. You might need to manually review the generated changelog file.

6. Update the Homebrew package:

• Check the commit ID for the released tag, e.g.: git show-ref v3.0.0
• Create a PR to update the odo-dev formula in Homebrew/homebrew-core repo (mainly :tag and :revision fields in odo.rb).

7. Create a PR to update the build/VERSION file with the latest version number.
8. Create a PR with a blog post. See this wiki page. If needed, update the versions labels in the docusaurus.config.js file
9. 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