82a4e247bf
Release management team has modified the way it releases projects and a new process and guideline has been established. This change adds support for the same. More information on this can be found at [1]. Within OpenStack, reno can be used to create release notes using the following command: tox -e venv -- reno new slug-goes-here where slug-goes-here is a prefix to your notes. More info on reno usage can be found at [2]. [1]: http://lists.openstack.org/pipermail/openstack-dev/2015-November/078301.html [2]: http://docs.openstack.org/developer/reno/usage.html Change-Id: Ic4c1d246b0c9dda7c4c3901ed9527481b6f8f3e3
21 lines
528 B
Plaintext
21 lines
528 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.
|
|
|
|
hacking<0.10,>=0.9.2
|
|
|
|
coverage>=3.6
|
|
discover
|
|
fixtures>=1.3.1
|
|
mock>=1.2
|
|
python-subunit>=0.0.18
|
|
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
|
|
oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0
|
|
testrepository>=0.0.18
|
|
testtools>=1.4.0
|
|
testscenarios>=0.4
|
|
WebTest>=2.0
|
|
# This is needed for subunit-trace
|
|
tempest-lib>=0.11.0
|
|
reno>=0.1.1 # Apache2
|