From 7479ff9c39e7c0703e8f55a465897f15f2730caa Mon Sep 17 00:00:00 2001 From: Tony Breeds Date: Thu, 29 Jun 2017 11:19:59 +1000 Subject: [PATCH] [doc] Add a few clarifying statements for stable branch guidelines Change-Id: I042c42330735bbff7f8c0faedecb0b8c08060e27 --- README.rst | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README.rst b/README.rst index fc5bf73f47..092b1546ff 100644 --- a/README.rst +++ b/README.rst @@ -424,12 +424,20 @@ Global-requirements These should be few and far between on stable branches, mainly masking known bad versions or in extreme adding a maximum version allowable for a package. -We work to remove these caps as well. +We work to remove these caps as well. Raising effective minimums is only +acceptable during `Phase I`, and only due to security issues. + +.. _Phase I: https://docs.openstack.org/project-team-guide/stable-branches.html#support-phases New requirements ++++++++++++++++ -In nearly all cases this is not allowed. +In nearly all cases this is not allowed. An example where this is allowed +would be: A dependency of a dependency has an issue that impacts OpenStack. +It wasn't listed in global-requirements.txt but it is required. In order to +block the affected releases and still be able to keep requirements in sync, we +list the library in global-requirements.txt and update all projects that +require it. Resources =========