Use reno for release notes

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>

doc/source/conf.py

@@ -23,7 +23,8 @@ sys.path.insert(0, os.path.abspath('../..'))
 extensions = [
     'sphinx.ext.autodoc',
     #'sphinx.ext.intersphinx',
-    'oslosphinx'
+    'oslosphinx',
+    'reno.sphinxext'
 ]
 
 # autodoc generation is a bit aggressive and a nuisance when doing heavy

doc/source/index.rst

@@ -16,6 +16,7 @@ Contents:
    installation
    usage
    contributing
+   releasenotes
 
 Design and Developer Docs
 ==========================

doc/source/releasenotes.rst

@@ -0,0 +1,5 @@
+===============
+ Release Notes
+===============
+
+.. release-notes::

releasenotes/notes/started-using-reno-8411d91eb3fe9e6c.yaml

@@ -0,0 +1,3 @@
+---
+other:
+  - Started using reno for release notes.

test-requirements.txt

@@ -15,3 +15,4 @@ testrepository>=0.0.18
 testscenarios>=0.4
 testtools>=1.4.0
 docker-py>=1.4.0 # Apache-2.0
+reno>=0.1.1 # Apache2