Andreas Jaeger d7f906b526 Remove setting of version/release from releasenotes ... Release notes are version independent, so remove version/release values. We've found that projects now require the service package to be installed in order to build release notes, and this is entirely due to the current convention of pulling in the version information. Release notes should not need installation in order to build, so this unnecessary version setting needs to be removed. This is needed for new release notes publishing, see I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting at http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html . Change-Id: Ia0c8d7dc346182fde095eebb82eeeb70fc1b9770		2017-11-16 20:46:56 +01:00
..
_static	Add reno for release notes management	2015-12-02 14:32:07 -06:00
_templates	Add reno for release notes management	2015-12-02 14:32:07 -06:00
20_releases.rst	Set up 3.x release notes	2016-06-07 17:34:38 -05:00
conf.py	Remove setting of version/release from releasenotes	2017-11-16 20:46:56 +01:00
index.rst	Update release/stable branch table in docs	2017-08-10 16:37:09 -05:00
mitaka.rst	Add mitaka release notes to master	2017-02-01 14:25:07 -06:00
newton.rst	Align '=' for developing.rst and newton.rst	2016-09-26 09:26:56 +08:00
ocata.rst	Update reno for stable/ocata	2017-01-31 23:36:54 +00:00
pike.rst	Update reno for stable/pike	2017-08-10 19:31:07 +00:00
pre_20_releases.rst	Fix typo in release notes	2016-12-26 15:30:53 +07:00
unreleased.rst	Update earliest-version number format in release notes	2016-12-22 13:49:27 +00:00