Add notes about stable merge requirements for sub-projects

It was pointed out the requirements around what is allowed to be merged
into stable Neutron sub-projects wasn't clear. This attempts to make
that a bit more refined so those who choose to participate in the Neutron
Stadium know these requirements.

Change-Id: I6d472f4d9458ce311199ded89dc2a81759d1efa5
Signed-off-by: Kyle Mestery <mestery@mestery.com>

diff --git a/doc/source/devref/sub_project_guidelines.rst b/doc/source/devref/sub_project_guidelines.rst
index 4396f14bdcdbc6526ac667259237b6f7b5d9ea11..b55b4863dca37a84c824c88ead6d6d89a01a21e7 100644 (file)
--- a/doc/source/devref/sub_project_guidelines.rst
+++ b/doc/source/devref/sub_project_guidelines.rst
@@ -114,6 +114,22 @@ team <https://review.openstack.org/#/admin/groups/539,members>`_.
 More info on stable branch process can be found on `the following page
 <https://wiki.openstack.org/wiki/StableBranch>`_.
 
+Stable merge requirements
+-------------------------
+
+Merges into stable branches are handled by members of the `neutron-stable-maint
+gerrit group <https://review.openstack.org/#/admin/groups/539,members>`_. The
+reason for this is to ensure consistency among stable branches, and compliance
+with policies for stable backports.
+
+For sub-projects who participate in the Neutron Stadium effort and who also
+create and utilize stable branches, there is an expectation around what is
+allowed to be merged in these stable branches. The Stadium projects should be
+following the stable branch policies as defined by on the `Stable Branch wiki
+<https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy>`_. This
+means that, among other things, no features are allowed to be backported into
+stable branches.
+
 Releases
 --------