From 4bdf575a07d6e7209613c78dd5969d4ee1cbadba Mon Sep 17 00:00:00 2001
From: SauloAislan <sauloa@lsd.ufcg.edu.br>
Date: Fri, 1 Jul 2016 19:16:55 +0000
Subject: [PATCH] Stable Branch URL Fixed

Change-Id: I294f67f1ded6f714ce5c45d0c6cd43e738fb61fb
---
 doc/source/stadium/sub_project_guidelines.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/source/stadium/sub_project_guidelines.rst b/doc/source/stadium/sub_project_guidelines.rst
index e7159bd2da2..212671e82fd 100644
--- a/doc/source/stadium/sub_project_guidelines.rst
+++ b/doc/source/stadium/sub_project_guidelines.rst
@@ -104,7 +104,7 @@ Subproject stable branches are supervised by horizontal `neutron-stable-maint
 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>`_.
+<http://docs.openstack.org/project-team-guide/stable-branches.html>`_.
 
 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
 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
+<http://docs.openstack.org/project-team-guide/stable-branches.html>`_. This
 means that, among other things, no features are allowed to be backported into
 stable branches.