From 0d5d4e9855eb0ca8b20042a84ba76f8b3673b750 Mon Sep 17 00:00:00 2001 From: Dirk Mueller Date: Sun, 4 Mar 2018 12:18:34 +0100 Subject: [PATCH] Add documentation for lower-constraints.txt Change-Id: I049dbaf3893a63aed3519ef5f25bfd3c62bdfdc4 --- README.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.rst b/README.rst index b15fa5277e..ae0ecea6eb 100644 --- a/README.rst +++ b/README.rst @@ -82,6 +82,12 @@ instance, if a dependency has dropped Python 2.7 support. ``upper-constraints.txt`` is machine generated and nothing more or less than an exact list of versions. +``lower-constraints.txt`` is manually maintained and can be consumed by projects +for tracking their individual project specific constraints as well as giving a +good indication to deployers what the global minimum requirements are +for the set of projects in the integrated gate. + + Enforcement for Test Runs ------------------------- @@ -176,6 +182,10 @@ dependencies. As such you should always generate a diff against the current merged constraints, otherwise your change may fail if it is incompatible with the current tested constraints. +A change to the minimum specified vesion of a library in ``global-requirements.txt`` +currenty requires adjusting the ``lower-constraints.txt`` file alongside with the +new constrainted coinstallable version of minimums. + Regenerating involves five steps. 1) Install the dependencies needed to compile various Python packages::