From c0798cbfe7bfde53c2e0f2773fb037bae0ede5dc Mon Sep 17 00:00:00 2001
From: Oliver Drotbohm <oliver.drotbohm@broadcom.com>
Date: Fri, 18 Oct 2024 09:30:24 +0200
Subject: [PATCH] GH-2241 - Polish release docs.

---
 etc/release.adoc | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/etc/release.adoc b/etc/release.adoc
index 3c8fc37a..a4c9c36c 100644
--- a/etc/release.adoc
+++ b/etc/release.adoc
@@ -12,8 +12,8 @@ The ones for Typinator are listed <<typinator-shortcuts, below>>.
 $ mvn release:prepare \
     -DreleaseVersion="1.2.3" \
     -DdevelopmentVersion="1.2.4-SNAPSHOT" \
-    -DscmReleaseCommitComment="4711 - Release version 1.2.3." \
-    -DscmDevelopmentCommitComment="4711 - Prepare next development iteration." \
+    -DscmReleaseCommitComment="GH-4711 - Release version 1.2.3." \
+    -DscmDevelopmentCommitComment="GH-4711 - Prepare next development iteration." \
     -Dtag="1.2.3"
 ----
 . Reset the release branch to the tag created
@@ -37,8 +37,6 @@ $ git push --force-with-lease
 This will kick of the CI workflows that fully publish the releases to the corresponding repositories.
 GA and service releases got to Maven Central, preview releases go to the Spring Artifactory.
 
-
-
 == Updating dependency versions
 
 Prior to a release we make sure that all dependencies have been updated to the latest ones corresponding to the policy applicable to the branch to be released.
@@ -117,7 +115,7 @@ git add . \
 mvn release:prepare \
   -DreleaseVersion="{{version=?Release version}}{{version}}" \
   -DdevelopmentVersion="{{devVersion=?Development version}}{{devVersion}}" \
-  -DscmReleaseCommitComment="{{ticketId=?Ticket}}{{ticketId}} - Release version {{version}}." \
-  -DscmDevelopmentCommitComment="{{ticketId}} - Prepare next development iteration." \
+  -DscmReleaseCommitComment="GH-{{ticketId=?Ticket}}{{ticketId}} - Release version {{version}}." \
+  -DscmDevelopmentCommitComment="GH-{{ticketId}} - Prepare next development iteration." \
   -Dtag="{{version}}"
 ----