Add note about requirements lower bounds
Since lower constraints job was removed the bounds are not actually tested. Add a note to explain the bounds are maintained on bast effort basis. Also remove note about old pip's behavior because recent pip can resolve dependencies without requiring specific order. Change-Id: I69a5d2c719ae84532697669edf5e0265e3949a42
This commit is contained in:
parent
8c2e94978b
commit
c67fa9dda4
@ -1,12 +1,3 @@
|
|||||||
# The order of packages is significant, because pip processes them in the order
|
|
||||||
# of appearance. Changing the order has an impact on the overall integration
|
|
||||||
# process, which may cause wedges in the gate later.
|
|
||||||
# Order matters to the pip dependency resolver, so sorting this file
|
|
||||||
# changes how packages are installed. New dependencies should be
|
|
||||||
# added in alphabetical order, however, some dependencies may need to
|
|
||||||
# be installed in a specific order.
|
|
||||||
#
|
|
||||||
# Requirements for docs
|
|
||||||
openstackdocstheme>=2.2.1 # Apache-2.0
|
openstackdocstheme>=2.2.1 # Apache-2.0
|
||||||
reno>=3.1.0 # Apache-2.0
|
reno>=3.1.0 # Apache-2.0
|
||||||
sphinx>=2.0.0,!=2.1.0 # BSD
|
sphinx>=2.0.0,!=2.1.0 # BSD
|
||||||
|
@ -1,12 +1,7 @@
|
|||||||
# The order of packages is significant, because pip processes them in the order
|
# Requirements lower bounds listed here are our best effort to keep them up to
|
||||||
# of appearance. Changing the order has an impact on the overall integration
|
# date but we do not test them so no guarantee of having them all correct. If
|
||||||
# process, which may cause wedges in the gate later.
|
# you find any incorrect lower bounds, let us know or propose a fix.
|
||||||
# Order matters to the pip dependency resolver, so sorting this file
|
|
||||||
# changes how packages are installed. New dependencies should be
|
|
||||||
# added in alphabetical order, however, some dependencies may need to
|
|
||||||
# be installed in a specific order.
|
|
||||||
#
|
|
||||||
# PBR should always appear first
|
|
||||||
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
||||||
python-zaqarclient>=1.0.0 # Apache-2.0
|
python-zaqarclient>=1.0.0 # Apache-2.0
|
||||||
Babel!=2.4.0,>=2.3.4 # BSD
|
Babel!=2.4.0,>=2.3.4 # BSD
|
||||||
|
@ -1,14 +1,4 @@
|
|||||||
# The order of packages is significant, because pip processes them in the order
|
|
||||||
# of appearance. Changing the order has an impact on the overall integration
|
|
||||||
# process, which may cause wedges in the gate later.
|
|
||||||
# Order matters to the pip dependency resolver, so sorting this file
|
|
||||||
# changes how packages are installed. New dependencies should be
|
|
||||||
# added in alphabetical order, however, some dependencies may need to
|
|
||||||
# be installed in a specific order.
|
|
||||||
#
|
|
||||||
# Hacking should appear first in case something else depends on pep8
|
|
||||||
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
||||||
|
|
||||||
|
|
||||||
coverage!=4.4,>=4.0 # Apache-2.0
|
coverage!=4.4,>=4.0 # Apache-2.0
|
||||||
testtools>=2.2.0 # MIT
|
testtools>=2.2.0 # MIT
|
||||||
|
Loading…
Reference in New Issue
Block a user