From 4d7d0058c3ba0b4e542ed7e964ee1056207b7a08 Mon Sep 17 00:00:00 2001 From: Nanne Baars Date: Wed, 20 Jun 2018 18:38:16 +0200 Subject: [PATCH] Update how to create a release document --- CREATE_RELEASE.MD | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/CREATE_RELEASE.MD b/CREATE_RELEASE.MD index f9199020d..d7d566313 100644 --- a/CREATE_RELEASE.MD +++ b/CREATE_RELEASE.MD @@ -12,18 +12,14 @@ At the moment we use Gitflow, for a release you create a new release branch and ``` git checkout develop git flow release start -mvn versions:set < -git commit -am "New release, updaing pom.xml" +mvn versions:set < +git commit -am "New release, updating pom.xml" git flow release publish +git push --tags ``` -Now we can make a new release, be sure you committed all your changes. +Now Travis takes over and will create the release in Github and on Docker Hub. -``` -git tag v8.0.0.M15 -git push origin v8.0.0.M15 -``` - -Now Travis takes over and will create the release in Github and on Docker Hub. +NOTE: the `mvn versions:set` command above is just there to make sure the master branch contains the latest version