From b0ddadbda52e352012c5ccaa6aee7c340c6ead3e Mon Sep 17 00:00:00 2001 From: Pavol Loffay Date: Wed, 11 Apr 2018 14:38:52 +0200 Subject: [PATCH] Fix release readme Signed-off-by: Pavol Loffay --- RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index 4e4b60423..7303c6a91 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -9,7 +9,7 @@ The release process consists of these steps: 1. Push the tag (`git push v0.20.0`) 1. Once the *tag* build finishes in Travis, the artifacts should have been uploaded to Sonatype staging, the staging repository closed, and the artifacts on the way to Maven Central (it takes 20min+ to get there). - In case of failures it is safe to retry by restarting the CROSSDOCK step of the build. If it keeps + In case of failures it is safe to retry by restarting the maven-deploy job. If it keeps failing, sometimes it may be necessary to close the staging repository manually. 1. Create a release on GitHub for the new tag. Use the changes from the `CHANGELOG` as the description. 1. Once the artifacts are available on Maven