From 718ca56ab3a2c14b05079bbea00968b59ee50714 Mon Sep 17 00:00:00 2001 From: Gunnar Morling Date: Wed, 19 Dec 2018 16:26:57 +0100 Subject: [PATCH] Update RELEASING.md --- RELEASING.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 36f3c7431..ff9c18bc1 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -210,11 +210,15 @@ Then, create a pull request with your changes and wait for a committer to approv When the blog post is available, use the [Debezium Twitter account](https://twitter.com/debezium) to announce the release by linking to the blog post. +When releasing a *final* version, send an e-mail to confluent-hub@confluent.io, asking to upload the new release artifacts, referening the tar.gz files on Maven Central. + # Automated Release -There are few manual steps to be completede before the execution +There are few manual steps to be completed before the execution: + * Update [the changelog](#update-the-changelog) * Update [configuration](#reconfigure-docker-hub-builds) for Docker Hub builds -To perform release automatically invoke a [Jenkins job](http://ci.hibernate.org/view/Debezium/job/debezium-release/). Two parameters are requested +To perform release automatically invoke a [Jenkins job](http://ci.hibernate.org/view/Debezium/job/debezium-release/). Two parameters are requested: + * `RELEASE_VERSION` - a version to be released in format x.y.z * `DEVELOPMENT_VERSION` - next development version in format x.y.z-SNAPSHOT