From a6b4830fbcd482893bb958166a39f50b072f7ad4 Mon Sep 17 00:00:00 2001
From: jem <michael.jerger@meissa-gmbh.de>
Date: Tue, 1 Feb 2022 09:06:00 +0100
Subject: [PATCH] release

---
 build.gradle    |  2 +-
 docs/Release.md | 21 ++++++++++++++++++---
 2 files changed, 19 insertions(+), 4 deletions(-)

diff --git a/build.gradle b/build.gradle
index 7e99295..c7eeb07 100644
--- a/build.gradle
+++ b/build.gradle
@@ -18,7 +18,7 @@ apply plugin: 'kotlinx-serialization'
 
 
 group = 'org.domaindrivenarchitecture.provs'
-version = '0.9.0-SNAPSHOT'
+version = '0.9.0'
 
 repositories {
     mavenCentral()
diff --git a/docs/Release.md b/docs/Release.md
index ed1aa37..ddc8049 100644
--- a/docs/Release.md
+++ b/docs/Release.md
@@ -1,8 +1,23 @@
 # How to create a release
 
 A release can be created by creating a git tag for a commit. The tag must follow this pattern: 
-v1.2 or v1.2.3
+release-1.2 or release-1.2.3
 
-I.e.: vX.X.Z where X, Y, Z are the major, minor resp. the patch level of the release. Z can be omitted.
+I.e.: release-X.X.Z where X, Y, Z are the major, minor resp. the patch level of the release. Z can be omitted.
 
-**Note:** Such kind of release tags should only be applied to commits in the master branch. 
\ No newline at end of file
+**Note:** Such kind of release tags should only be applied to commits in the master branch.
+
+```
+#adjust [version]
+vi build.gradle
+
+# release via git
+git commit -am "release"
+git tag -am "release" release-[release version no]
+git push --follow-tags
+
+# bump version - increase version and add -SNAPSHOT
+vi build.gradle
+git commit -am "version bump"
+git push
+```
\ No newline at end of file