Add reno releasenotes support

Do it a little bit differently than OpenStack and just put the
releasenotes into the documentation.

Add an initial release note with no contents so that the build flow and docs
integration can be verified. The note file can be removed later.

Change-Id: Iad16b575e2abbea997b64e3c0e5aa1497b4ff0d2

doc/source/conf.py

@@ -26,7 +26,8 @@ sys.path.insert(0, os.path.abspath('../..'))
 # Add any Sphinx extension module names here, as strings. They can be extensions
 # coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
 extensions = [ 'sphinxcontrib.programoutput',
-               'sphinxcontrib.httpdomain']
+               'sphinxcontrib.httpdomain',
+               'reno.sphinxext']
 #extensions = ['sphinx.ext.intersphinx']
 #intersphinx_mapping = {'python': ('http://docs.python.org/2.7', None)}
 

doc/source/index.rst

@@ -15,6 +15,7 @@ Contents:
    configuration
    operation
    devguide
+   releasenotes
 
 Indices and tables
 ==================

doc/source/releasenotes.rst

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

releasenotes/notes/initial-note-f7414710196b7198.yaml

@@ -0,0 +1,4 @@
+---
+prelude: >
+    Initial release note. This note should be removed as soon as we have a
+    real one.

test-requirements.txt

@@ -4,6 +4,7 @@ coverage
 sphinx>=1.5.1,<1.6
 sphinxcontrib-programoutput
 sphinxcontrib-httpdomain
+reno>=2.5.0 # Apache-2.0
 fixtures>=0.3.12
 mock>=1.0
 python-subunit