openstack/requirements
Code Issues Proposed changes

Add horizon to upper-constraints

Browse Source 
horizon plugins use horizon as a library.
Having horizon in upper-constraints would be helpful
to avoid unexpected breakage due to a newer horizon releases,
particularly in stable branches.

The reason we don't have horizon in upper-constraints so far is
because most horizon plugins would like to work and test with horizon
in a same branch, but Zuul v3 allows such tests.
This reasoning is no longer true.

Updated to stable/train maximum of 16.0.0.

Note that this is proposed to stable branches directly.
In the master branch, it is required to split out common portions
in horizon into a separate deliverable and it was rejected to
add horizon to upper-constraints.txt.

Change-Id: I421ee2d498ea5100d9b52e356b46f2d594638b5b
This commit is contained in:
Akihiro Motoki 2019-12-23 15:47:46 +09:00
parent bfd4804c47
commit 3e54878f9c
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
blacklist.txt
View File

@ -16,10 +16,9 @@ pycodestyle
pylint
Pygments
# The following horizon and Neutron libraries need to be blacklisted
# The following Neutron libraries need to be blacklisted
# as they do not use cycle-with-intermediary. The only time they
# would be updated is at release time.
horizon
networking-bagpipe
networking-bgpvpn
networking-l2gw

1
upper-constraints.txt
View File

@ -691,3 +691,4 @@ scikit-learn===0.21.3;python_version=='3.4'
scikit-learn===0.21.3;python_version=='3.5'
scikit-learn===0.21.3;python_version=='3.6'
scikit-learn===0.21.3;python_version=='3.7'
horizon===16.0.0