diff --git a/doc/source/reference/release_models.rst b/doc/source/reference/release_models.rst
index 3b8ab93a30..98e9a16d1d 100644
--- a/doc/source/reference/release_models.rst
+++ b/doc/source/reference/release_models.rst
@@ -147,18 +147,6 @@ two options: develop the new feature in a new library depending on the
 stable one, or grant an exception and switch it back to the
 `cycle-with-intermediary`_ model.
 
-Adding Deliverables
-===================
-
-In order to be considered to be included in the release for a given
-series, the project must be documented by adding a deliverable file to
-this repository before the second milestone of the series.
-
-Projects created or added to governance after the second milestone
-should be released using the independent release model, and then
-changed to one of the cycle-based models at the start of the next
-cycle.
-
 Legacy release models
 =====================
 
diff --git a/doc/source/reference/using.rst b/doc/source/reference/using.rst
index f06beb3f53..347b85138e 100644
--- a/doc/source/reference/using.rst
+++ b/doc/source/reference/using.rst
@@ -28,6 +28,14 @@ detail below. All automated manipulation of the deliverable is managed
 through the data file, which is reviewed by the core team when the
 patch is proposed to openstack/releases.
 
+Adding Deliverables
+===================
+
+In order to be considered to be included in the release for a given
+series, the project must be documented by adding a deliverable file to
+this repository before the second milestone of the series. Exceptions
+will be considered by the release team on a case-by-case basis.
+
 Requesting a Release
 ====================