Skip to content

Latest commit

 

History

History
39 lines (26 loc) · 1.38 KB

RELEASE.md

File metadata and controls

39 lines (26 loc) · 1.38 KB
Raw

Releasing the Jaeger Operator for Kubernetes

  1. Update Jaeger version in versions.txt

  2. Make sure the new version is present at pkg/upgrade/versions.go

  3. Prepare a changelog since last release. Get the OAUTH_TOKEN from (Github)[https://github.com/settings/tokens/new?description=GitHub%20Changelog%20Generator%20token] and select repo:status scope.

    OAUTH_TOKEN=... make changelog

  4. Commit version change and changelog and create a pull request:

    git commit -sm "Preparing relase v1.22.0"

  5. Tag and push

    git checkout master ## it's only possible to release from master for now!
git tag release/v1.22.0
git push [email protected]:jaegertracing/jaeger-operator.git release/v1.22.0

  6. Wait until release CI job finishes and then pull the changes:

    git pull [email protected]:jaegertracing/jaeger-operator.git master

  7. Apply generated OLM catalog files to operatorhub.io

    • Clone the operatorhub repo
    • Run make operatorhub
      • If you have hub installed and configured, it will open the necessary PRs for you automatically. Hint: dnf install hub works fine on Fedora.
      • If you don't have it, the branches will be pushed to origin and you should be able to open the PR from there