Expand the version management guidelines (Azure#17277)

Author: alzimmermsft

eng/versioning/version_client.txt

@@ -12,12 +12,22 @@
 # com.azure:azure-example as a dependency.
 #
 # When releasing a library the current-version should be set to the version being released to Maven. Upon release of the
-# library an automated PR will be submitted to update the dependency-version to the version that was released and the
-# dependency-version to the next in development version.
+# library an automated PR will be submitted to update the dependency-version and current-version, the updates are
+# dependent on the current and previous releases of the library.
 #
-# The next in development version is determined by the version that was released.
-# - If a beta version was released the beta number is incremented. (1.2.0-beta.1 -> 1.2.0-beta.2)
-# - If a GA version was released the current-version is the next minor beta. (1.2.0 -> 1.3.0-beta.1)
+# - When both dependency and current are beta both versions will update upon release. Given the version release state
+#   of 1.0.0-beta.2;1.0.0-beta.3 the updated versions will become 1.0.0-beta.3;1.0.0-beta.4.
+#
+# - When both dependency and current are GA both versions will update upon release. Given the version release state of
+#   1.0.0;1.0.1 the updated versions will become 1.0.1;1.1.0-beta.1. Current version will always become the next minor
+#   beta version.
+#
+# - When dependency is GA and current is beta only the current version will update upon release. Given the version
+#   release state of 1.0.0;1.1.0-beta.1 the updated versions will become 1.0.0;1.1.0-beta.2. The dependency version will
+#   remain as-is as GA libraries could depend on the library being released, if they were to take a beta dependencies it
+#   could result in an invalid release state (GA libraries can never have beta dependencies). The current version will
+#   become the next beta increment version. If a library requires the released beta version as a dependency view the
+#   beta dependency guidelines below.
 #
 # When adding a new library the dependency-version and current-version will be the same until the first release is
 # performed. So, if com.azure:azure-new-library is added with major version 2 it'll use