re #500: Update version numbers in other places.

[skip ci]

doc/INSTALL-buildout.rst

@@ -125,8 +125,8 @@ This procedure involves the following steps:
 - Fetch the buildout bootstrap script into the environment.
 
 - Fetch the version files into the environment, for example:
-  https://raw.github.com/zopefoundation/Zope/2.13.27/versions.cfg
-  https://raw.github.com/zopefoundation/Zope/2.13.27/ztk-versions.cfg
+  https://raw.github.com/zopefoundation/Zope/2.13.29/versions.cfg
+  https://raw.github.com/zopefoundation/Zope/2.13.29/ztk-versions.cfg
 
 - Create a buildout configuration as follows:
 

doc/WSGI.rst

@@ -14,7 +14,7 @@ To run as a WSGI application, you need to install some additional software.
 
    $ bin/pip install \
     --no-binary zc.recipe.egg \
-    -r https://zopefoundation.github.io/Zope/releases/2.13.27/requirements.txt \
+    -r https://zopefoundation.github.io/Zope/releases/2.13.29/requirements.txt \
     repoze.who repoze.tm2 repoze.retry Paste PasteDeploy PasteScript
    Collecting repoze.who
    ...

doc/maintainers/RELEASING.rst

@@ -10,7 +10,7 @@ branch, based on the ``2.13`` branch, as the locus for those changes:
 
 .. code-block:: bash
 
-   $ git checkout -b 2.13.23-prep 2.13
+   $ git checkout -b 2.13.30-prep 2.13
 
 Update the release version in ``setup.py``
 ------------------------------------------
@@ -20,7 +20,7 @@ Set the new release version, and commit:
 .. code-block:: bash
 
    $ vim setup.py
-   $ git commit -m "Update version for 2.13.23 release" setup.py
+   $ git commit -m "Update version for 2.13.30 release" setup.py
 
 Pin versions in ``buildout.cfg``
 --------------------------------
@@ -81,7 +81,7 @@ without buildout. Be sure to:
 
    $ vim requirements.txt
    $ git add requirements.txt
-   $ git commit -m "Pin versions for 2.13.23 release" buildout.cfg requirements.txt
+   $ git commit -m "Pin versions for 2.13.30 release" buildout.cfg requirements.txt
 
 Review / update the changelog
 -----------------------------
@@ -91,7 +91,7 @@ Add today's date to the current release.
 .. code-block:: bash
 
    $ vim doc/CHANGES.rst
-   $ git commit -m "Finalize changelog 2.13.23 release" doc/CHANGES.rst
+   $ git commit -m "Finalize changelog 2.13.30 release" doc/CHANGES.rst
 
 .. note::
 
@@ -103,7 +103,7 @@ Tag the release
 
 .. code-block:: bash
 
-   $ git tag -sm "Tag 2.13.23 release" 2.13.23
+   $ git tag -sm "Tag 2.13.30 release" 2.13.30
 
 .. note::
 
@@ -126,7 +126,7 @@ Push the git release artefacts
 
 .. code-block:: bash
 
-   $ git push origin 2.13.23-prep && git push --tags
+   $ git push origin 2.13.30-prep && git push --tags
 
 Update the ``2.13`` branch for the next release
 -----------------------------------------------
@@ -191,9 +191,9 @@ In the next line replace the two version numbers with the current release:
 
 .. code-block:: bash
 
-   $ bin/z2_kgs 2.13.23 /var/www/download.zope.org/Zope2/index/2.13.23/
+   $ bin/z2_kgs 2.13.30 /var/www/download.zope.org/Zope2/index/2.13.30/
 
-Visit ``http://download.zope.org/Zope2/index/2.13.23/`` and make sure
+Visit ``http://download.zope.org/Zope2/index/2.13.30/`` and make sure
 a ``Zope2`` folder with an ``index.html`` was created.
 
 If this is missing, you forgot to add ``Zope2`` to the ``[versions]``