RELEASE.md

Releasing the Jaeger Operator for Kubernetes

1. Make sure the jaeger.version file is up to date

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

3. Prepare a changelog and get it merged. A list of commits since the last release (v1.8.0 in the following example) can be obtained via:

   $ git log --format="format:* %s" v1.8.0...HEAD
   

4. Test!

   export BUILD_IMAGE_TEST="${USER}/jaeger-operator:latest"
   export BUILD_IMAGE="${BUILD_IMAGE_TEST}"
   make all
   

5. Tag and push

   git checkout master ## it's only possible to release from master for now!
   git tag release/v1.6.1
   git push git@github.com:jaegertracing/jaeger-operator.git release/v1.6.1
   

6. Apply generated OLM catalog files to operatorhub.io

   • Retrieve the auto-generated operator manifests, e.g. git pull upstream master
   • Clone the operatorhub repo
   • Apply the following changes to community-operators/jaeger and upstream-community-operators/jaeger in separate PRs:
     • overwrite the file jaeger-package.yaml from deploy/olm-catalog in jaeger-operator repo
     • copy the jaeger.clusterserviceversion.yaml and rename to include the version, e.g. jaeger.<version>.clusterserviceverson.yaml