openstack
/
requirements
Code Issues Proposed changes

Add documentation for lower-constraints.txt 

Change-Id: I049dbaf3893a63aed3519ef5f25bfd3c62bdfdc4
This commit is contained in:
Dirk Mueller 2018-03-04 12:18:34 +01:00
parent 1e604447eb
commit 0d5d4e9855
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.rst
View File

@ -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::