openstack/neutron
Code Issues Proposed changes

Note fullstack depends on released neutronclient

Browse Source 
Note in TESTING.rst that fullstack tests that depend on changes to
python-neutronclient to execute need to wait until there is a released
version of python-neutronclient before they will work in the gate.

Change-Id: I1d32c65f0c941cf8f163a441258faa34b50ff88f
This commit is contained in:
Nate Johnston 2016-03-24 10:20:18 -04:00 committed by Nate Johnston
parent b54abb1baf
commit c064258886
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
TESTING.rst
View File

@ -241,6 +241,16 @@ databases, so can a RabbitMQ server serve multiple messaging domains.
Exchanges and queues in one 'vhost' are segmented from those in another
'vhost'.
Please note that if the change you would like to test using fullstack tests
involves a change to python-neutronclient as well as neutron, then you should
make sure your fullstack tests are in a separate third change that depends on
the python-neutronclient change using the 'Depends-On' tag in the commit
message. You will need to wait for the next release of python-neutronclient,
and a minimum version bump for python-neutronclient in the global requirements,
before your fullstack tests will work in the gate. This is because tox uses
the version of python-neutronclient listed in the upper-constraints.txt file in
the openstack/requirements repository.
When?
+++++