fe41d0a502
As part of the Denver PTG [1] we decided networking related projects that are "current" and want to receive neutron-lib consumption patches on an on-going basis should indicate such with a well defined comment in their requirements.txt. This allows us to easily find the list of project to receive neutron-lib consumption patches [2] by searching for the string. In addition, projects opting-in for these patches are also attesting they will stay up to date with TC and infra initiatives to ensure consumption patches can flow freely. This patch adds the "neutron-lib-current" string to requirements.txt opting in for neutron-lib consumption patches. [1] https://etherpad.openstack.org/p/neutron-stein-ptg [2] https://docs.openstack.org/neutron-lib/latest/contributor/contributing.html#phase-4-consume Change-Id: Ie153c218d631ad373881d8bf39617b8483342988
27 lines
1017 B
Plaintext
27 lines
1017 B
Plaintext
# 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.
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
|
|
eventlet!=0.18.3,!=0.20.1,>=0.18.2 # MIT
|
|
httplib2>=0.9.1 # MIT
|
|
netaddr>=0.7.18 # BSD
|
|
SQLAlchemy>=1.2.0 # MIT
|
|
alembic>=0.8.10 # MIT
|
|
six>=1.10.0 # MIT
|
|
neutron-lib>=1.18.0 # Apache-2.0
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
oslo.db>=4.27.0 # Apache-2.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
oslo.messaging>=5.29.0 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.service!=1.28.1,>=1.24.0 # Apache-2.0
|
|
oslo.utils>=3.33.0 # Apache-2.0
|
|
neutron>=13.0.0.0b2 # Apache-2.0
|
|
|
|
# The comment below indicates this project repo is current with neutron-lib
|
|
# and should receive neutron-lib consumption patches as they are released
|
|
# in neutron-lib. It also implies the project will stay current with TC
|
|
# and infra initiatives ensuring consumption patches can land.
|
|
# neutron-lib-current
|