7e1db55245
Our HACKING documentation instructs developers to use: "tox -e venv -- reno new <slug>" to create new release notes. We did not add reno to our requirements though, so attempting to run "tox -e venv -- reno" fails with the command not found. This adds reno to our requirements so they get installed in the venv. Change-Id: Ie888297098e9380587769affad1a8ca9a6dfe5bc Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
16 lines
596 B
Plaintext
16 lines
596 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 already pins down pep8, pyflakes and flake8
|
|
hacking!=0.13.0,<0.14,>=0.12.0 # Apache-2.0
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
ddt>=1.0.1 # MIT
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
mock>=2.0.0 # BSD
|
|
reno>=2.5.0 # Apache-2.0
|
|
requests-mock>=1.2.0 # Apache-2.0
|
|
tempest>=17.1.0 # Apache-2.0
|
|
testtools>=2.2.0 # MIT
|
|
stestr>=1.0.0 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|