Merge "Clarify inability to delete tags"

doc/source/creators.rst

@@ -913,8 +913,8 @@ such as installation, configuration, and administration. Follow the layout
 of project documentation as described in `Project guide setup
 <https://docs.openstack.org/doc-contrib-guide/project-guides.html>`_.
 
-Tagging a Release
------------------
+Tagging an Initial Release
+--------------------------
 
 To verify that the release machinery works, push a signed tag to the
 "gerrit" remote. Use the smallest version number possible. If this is
@@ -943,6 +943,9 @@ If you need to check the logs, you can use the `git-os-job`_ command:
 
 .. _git-os-job: https://pypi.python.org/pypi/git-os-job
 
+See :ref:`tagging-a-release` in the Project Driver's Guide for more
+detail on tag pushing workflows.
+
 Allowing Other OpenStack Projects to Use Your Library
 =====================================================
 

doc/source/drivers.rst

@@ -225,6 +225,8 @@ to reviewers to identify files which need extra attention.
 You can learn more about `stable branches in the project team guide
 <https://docs.openstack.org/project-team-guide/stable-branches.html>`_.
 
+.. _tagging-a-release:
+
 Tagging a Release
 ~~~~~~~~~~~~~~~~~
 
@@ -248,6 +250,11 @@ and push that tag to Gerrit by running the following commands::
 
 .. note::
 
+  * Tags can't be effectively deleted once pushed, so make absolutely
+    certain they're correct (ideally by locally testing release
+    artifact generation commands and inspecting the results between
+    the tag and push steps above).
+
   * Git won't have a remote named gerrit until the first time git-review
     runs. You may need to run ``git review -s`` before the push.