openstack/python-cinderclient
Code Issues Proposed changes

Add reno to requirements

Browse Source 
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>
This commit is contained in:
Sean McGinnis
2018-07-23 11:52:17 -05:00
parent 4536b2fb9f
commit 7e1db55245
2 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
lower-constraints.txt
View File

@@ -47,6 +47,7 @@ python-mimeparse==1.6.0
python-subunit==1.0.0 python-subunit==1.0.0
pytz==2013.6 pytz==2013.6
PyYAML==3.12 PyYAML==3.12
reno==2.5.0
requests-mock==1.2.0 requests-mock==1.2.0
requests==2.14.2 requests==2.14.2
rfc3986==0.3.1 rfc3986==0.3.1

1
test-requirements.txt
View File

@@ -7,6 +7,7 @@ coverage!=4.4,>=4.0 # Apache-2.0
ddt>=1.0.1 # MIT ddt>=1.0.1 # MIT
fixtures>=3.0.0 # Apache-2.0/BSD fixtures>=3.0.0 # Apache-2.0/BSD
mock>=2.0.0 # BSD mock>=2.0.0 # BSD
reno>=2.5.0 # Apache-2.0
requests-mock>=1.2.0 # Apache-2.0 requests-mock>=1.2.0 # Apache-2.0
tempest>=17.1.0 # Apache-2.0 tempest>=17.1.0 # Apache-2.0
testtools>=2.2.0 # MIT testtools>=2.2.0 # MIT