openstack/neutron
Code Issues Proposed changes

Stable Branch URL Fixed

Browse Source 
Change-Id: I294f67f1ded6f714ce5c45d0c6cd43e738fb61fb
This commit is contained in:
SauloAislan 2016-07-01 19:16:55 +00:00
parent 00f95afaae
commit 4bdf575a07
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/stadium/sub_project_guidelines.rst
View File

@ -104,7 +104,7 @@ Subproject stable branches are supervised by horizontal `neutron-stable-maint
team <https://review.openstack.org/#/admin/groups/539,members>`_. team <https://review.openstack.org/#/admin/groups/539,members>`_.
More info on stable branch process can be found on `the following page More info on stable branch process can be found on `the following page
<https://wiki.openstack.org/wiki/StableBranch>`_. <http://docs.openstack.org/project-team-guide/stable-branches.html>`_.
Stable merge requirements Stable merge requirements
------------------------- -------------------------
@ -118,7 +118,7 @@ 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 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 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 following the stable branch policies as defined by on the `Stable Branch wiki
<https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy>`_. This <http://docs.openstack.org/project-team-guide/stable-branches.html>`_. This
means that, among other things, no features are allowed to be backported into means that, among other things, no features are allowed to be backported into
stable branches. stable branches.