From f12f38761aa4c4f77cea316e6a9f4d0c09a95b5f Mon Sep 17 00:00:00 2001 From: Kyle Mestery Date: Thu, 29 Oct 2015 10:00:24 +0900 Subject: [PATCH] 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 --- doc/source/devref/sub_project_guidelines.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/doc/source/devref/sub_project_guidelines.rst b/doc/source/devref/sub_project_guidelines.rst index 4396f14bd..b55b4863d 100644 --- a/doc/source/devref/sub_project_guidelines.rst +++ b/doc/source/devref/sub_project_guidelines.rst @@ -114,6 +114,22 @@ team `_. More info on stable branch process can be found on `the following page `_. +Stable merge requirements +------------------------- + +Merges into stable branches are handled by members of the `neutron-stable-maint +gerrit group `_. 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 +`_. This +means that, among other things, no features are allowed to be backported into +stable branches. + Releases -------- -- 2.45.2