openstack-manuals/test-requirements.txt
Adam Spiers 58dbdffcf2 prepare to use reno from Pike onwards
A stated goal from the Atlanta PTG this week was to use reno for our
release notes from Pike onwards.  This requires reno to support
configurable sections, which have been added by:

    https://review.openstack.org/#/c/436639

Once this is merged into reno, this commit configures openstack-manuals
so that reno will work with it, and a build of releasenotes/ will
automatically include a reno-generated report via reno's sphinx
extension.

Depends-on: I914572c6a07ca81c54965b4b5a6b6aba50b3a787
Change-Id: Id029f462fb553b3429629b90585e2790734f1bb9
2017-02-23 18:22:25 -05:00

23 lines
696 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>=1.6 # Apache-2.0
# Hacking already pins down pep8, pyflakes and flake8
hacking<0.12,>=0.11.0 # Apache-2.0
beautifulsoup4 # MIT
Jinja2>=2.8 # BSD License (3 clause)
openstack-doc-tools>=1.1.0 # Apache-2.0
sphinx>=1.5.1,<1.6 # BSD
openstackdocstheme>=1.5.0 # Apache-2.0
doc8 # Apache-2.0
requests>=2.10.0,!=2.12.2 # Apache-2.0
requestsexceptions>=1.1.1 # Apache-2.0
reno>=2.1.0 # Apache-2.0
sphinxmark # Apache-2.0
lxml>=2.3,!=3.7.0 # BSD
# For translations
Babel>=2.3.4 # BSD