[#1391] Update release guide docs

Author: ReeceHumphreys

docs/source/Support/Developer/releaseGuide.rst

@@ -72,17 +72,29 @@ back into ``develop`` to ensure they are included in future releases.
 
 Creating and Pushing Tags
 -------------------------
-Releases are published by pushing a git tag to the ``master`` branch. Our GitHub Actions workflow
-(``Publish Wheels``) is triggered on tag pushes matching:
-
-- ``v[0-9]*``  (real releases, published to PyPI)
+Releases are published by pushing a git tag. The ``Publish Wheels`` GitHub Actions
+workflow triggers on tag pushes and routes artifacts based on the tag name:
+
+.. list-table::
+   :header-rows: 1
+   :widths: 30 70
+
+   * - Tag pattern
+     - Destination
+   * - ``vX.Y.Z`` (no ``rc``)
+     - PyPI (public release)
+   * - ``vX.Y.ZrcN``
+     - TestPyPI (release candidate)
+   * - ``test*``
+     - TestPyPI (ad-hoc testing)
 
 This means: **pushing a tag kicks off the wheel builds on all supported
 platforms, builds an sdist, and then publishes the artifacts**.
 
 Tag format
 ^^^^^^^^^^
-Release tags must follow the format ``vX.Y.Z`` (for example, ``v2.9.0``).
+- Full release tags must follow the format ``vX.Y.Z`` (for example, ``v2.9.0``).
+- Release candidate tags follow ``vX.Y.ZrcN`` (for example, ``v2.10.2rc1``).
 
 Where to tag
 ^^^^^^^^^^^^