The release job should:

• Check that all issues of the version to be released are in state "Resolved"
• Transition the issues from "Resolved" to "Closed"
• Release the release
• Use debezium-builder account

It also seems we didn't cut a release of the Postgres Logical Decoder plug-in for 0.5.2. The Docker file still points to 0.5.1: https://hub.docker.com/r/debezium/postgres/~/dockerfile/

It's not a big issue as the plug-in has been changed, but I'd strongly prefer to re-tag it with every release so to stay on one single release version across all components (i.e. this should still be done for 0.5.2).

Extending RELEASING.md

• Document how to start the automated release process
• Document the steps above
• Document Docker Hub reconfiguration when a new image stream is created (major or minor version change) - it seems there is no API for automated change

Backup

• Use Jenkins Job builder to create job generation scripts for jobs http://ci.hibernate.org/view/Debezium/