From ffd165a7f2751795b6a17042aa448193d404ed9d Mon Sep 17 00:00:00 2001
From: "Achim D. Brucker" <adbrucker@0x5f.org>
Date: Sat, 27 Oct 2018 10:50:07 +0100
Subject: [PATCH] Updated instructions how to update version strings.

---
 README.md | 22 ++++++++++++++++++----
 1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 39caa8a3c..55ac39fcd 100644
--- a/README.md
+++ b/README.md
@@ -46,19 +46,33 @@ comLogicalhackingArtifactsPassword=<PASSWORD>
 
 ### Preparation
 
-Before publishing new artifacts to the artifacts repository, please update the version identifier in
-the file  `build.gradle` by replacing the second `SNAPSHOT`
+Before publishing new artifacts to the artifacts repository, please update the version identifier in the file  `build.gradle` by removing the second `SNAPSHOT`
+and updating the `<VERSION>` identifier.
 
 ``` gradle
-version '1.5.1-SNAPSHOT-DASCA-SNAPSHOT'
+version '1.5.1-SNAPSHOT-DASCA-<VERSION>-SNAPSHOT'
 ```
 
-with the version that should be published. Next, tag the new version:
+with the version that should be published. Next, commit your changes and tag the
+new version:
 
 ``` gradle
+git commit -m "Preparing release of version <VERSION>." build.gradle
 git tag -s "<VERSION>" -m "Tagging version <VERSION>."
 ```
 
+Finally, mark the development version by appending `-SNAPSHOT`
+
+``` gradle
+version '1.5.1-SNAPSHOT-DASCA-<VERSION>-SNAPSHOT'
+```
+
+and commit your changes:
+
+``` gradle
+git commit -m "Marked development version" build.gradle
+```
+
 ### Uploading Artifacts
 
 Publishing artifacts is as easy as calling