diff --git a/doc/source/contributor/policies/index.rst b/doc/source/contributor/policies/index.rst
index 32cc11f87b..c1d030aa6a 100644
--- a/doc/source/contributor/policies/index.rst
+++ b/doc/source/contributor/policies/index.rst
@@ -11,3 +11,4 @@ This page collects basic policies on horizon development.
    horizon-groups
    core-reviewers
    horizon-bugs
+   releasing
diff --git a/doc/source/contributor/policies/releasing.rst b/doc/source/contributor/policies/releasing.rst
new file mode 100644
index 0000000000..75ff83a7e8
--- /dev/null
+++ b/doc/source/contributor/policies/releasing.rst
@@ -0,0 +1,41 @@
+==========================
+Releasing Horizon Projects
+==========================
+
+Since the responsibility for releases will move between people, we document
+that process here.
+
+A full list of projects that horizon manages is available in the
+`governance site <https://governance.openstack.org/reference/projects/horizon.html>`__.
+
+Who is responsible for releases?
+--------------------------------
+
+The current PTL is ultimately responsible for making sure code gets released.
+They may choose to delegate this responsibility to a liaison, which is
+documented in the `cross-project liaison wiki
+<https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management>`__.
+
+Anyone may submit a release request per the process below, but the PTL or
+liaison must +1 the request for it to be processed.
+
+Release process
+---------------
+
+Releases are managed by the OpenStack release team. The release process is
+documented in the `Project Team Guide
+<https://docs.openstack.org/project-team-guide/release-management.html#how-to-release>`__.
+
+In general, horizon deliverables follow the `cycle-with-intermediary
+<https://releases.openstack.org/reference/release_models.html#cycle-with-intermediary>`__
+release model.
+
+Things to do before releasing
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+* Update default policy-in-code rules in horizon for all backend services
+  like cinder/glance/keystone/neutron/nova. For more information on how to
+  update these policy rules see the :doc:`/contributor/topics/policy`.
+* Check for any open patches that are close to be merged or release critical.
+  This usually includes important bug fixes and/or features that we'd
+  like to release, including the related documentation.