commit 48c55c1d06762cec650ae486dcca023bcd7eb2de
author Nasser Grainawi <nasser.grainawi@linaro.org> Tue Jan 24 20:37:37 2023 +0000
committer Gerrit Code Review <noreply-gerritcodereview@google.com> Tue Jan 24 20:37:37 2023 +0000
tree 92f84e58a18a3218c395961953cd5c817197cd20
parent 717a30f1dee700e8bdef92aab96247d69be15c2b
parent ad155adbee5714d555bda2e309e62e7e40954439

Merge "Docs: Use semantic versioning compatible tag example"

Documentation/developer-guide.md

diff --git a/Documentation/developer-guide.md b/Documentation/developer-guide.md
index 6f809fd..5b64e5e 100644
--- a/Documentation/developer-guide.md
+++ b/Documentation/developer-guide.md
@@ -183,7 +183,7 @@
 ```
 
 Tag the release with a signed, annotated tag matching the version number, for
-example "v0.4-1".
+example "v1.1.0".
 
 Once released, Maven projects can consume the new version as long as they point
 at the proper repository URL. Similarly, Bazel projects using the `maven_jar`