diff --git a/doc/source/contributor/releasecycle.rst b/doc/source/contributor/releasecycle.rst
index 7d1100fccb6..bc25f6e5517 100644
--- a/doc/source/contributor/releasecycle.rst
+++ b/doc/source/contributor/releasecycle.rst
@@ -55,6 +55,35 @@ Between PTG and Milestone-1
 
    Example patch: https://review.opendev.org/c/opendev/irc-meetings/+/695339
 
+#. **Supported Python versions**
+
+   * The supported Python runtimes for the cycle may have changed from the
+     previous cycle.  You can find them at
+     https://governance.openstack.org/tc/reference/runtimes/
+
+   * Review the tox testenvs defined in ``tox.ini`` and make sure there
+     are functional testenvs for each.  You don't have to worry about
+     unit tests--tox is smart enough to know what to do for those--but
+     if you specify ``tox -e functional-py312`` tox will bomb unless
+     there's a 'functional-py312' testenv defined.
+
+   * The OpenStack required check and gate tests are defined in a template
+     in `zuul.d/project-templates.yaml`_ in the
+     `openstack/openstack-zuul-jobs repo`_.  The template is maintained by
+     the OpenStack QA team.  It should have an easily recognizable name,
+     for example, ``openstack-python3-zed-jobs``.
+
+     Usually there will be autogenerated patches for each cinder project
+     repo to change the template from the previous cycle's to the current
+     cycle's, so watch for those.  Or you can proactively make the changes
+     yourself as soon as the template is available.
+
+     Example new template patch:
+     https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/831826
+
+     .. _zuul.d/project-templates.yaml: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/project-templates.yaml
+     .. _openstack/openstack-zuul-jobs repo: https://opendev.org/openstack/openstack-zuul-jobs
+
 #. Focus on spec reviews to get them approved and updated early in
    the cycle to allow enough time for implementation.