
The OpenStack Release team has enabled support for reno for release notes across all projects [1]. Start using this for Kuryr. Note that Kuryr has no stable/liberty branch, so similar to shade [2], we'll just tuck in the release notes into the general documentation area for now. [1] http://docs.openstack.org/developer/reno/ [2] https://review.openstack.org/#/c/253597/ Change-Id: I3b172f25fe454253fd82f138ed012f35a47c2eb9 Signed-off-by: Kyle Mestery <mestery@mestery.com>
19 lines
489 B
Plaintext
19 lines
489 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.11,>=0.10.0
|
|
|
|
coverage>=3.6
|
|
ddt>=0.7.0
|
|
python-subunit>=0.0.18
|
|
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
|
|
oslosphinx>=2.5.0 # Apache-2.0
|
|
oslotest>=1.7.0 # Apache-2.0
|
|
testrepository>=0.0.18
|
|
testscenarios>=0.4
|
|
testtools>=1.4.0
|
|
docker-py>=1.4.0 # Apache-2.0
|
|
reno>=0.1.1 # Apache2
|