From 7c1e759e4dff088cda82875b8b1d8edbd36418dd Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Fri, 17 Nov 2017 10:30:01 +0100 Subject: [PATCH] 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: I44534ae7990efb3c2cc1abb0fa5dd2e26a5d3142 --- releasenotes/source/conf.py | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/releasenotes/source/conf.py b/releasenotes/source/conf.py index 6bb3a14..ed16c2b 100644 --- a/releasenotes/source/conf.py +++ b/releasenotes/source/conf.py @@ -59,14 +59,12 @@ project = u'Valet Release Notes' copyright = u'2017, Valet Authors' author = u'Valet Authors' -# The version info for the project you're documenting, acts as replacement for -# |version| and |release|, also used in various other places throughout the -# built documents. -# +# Release notes do not need a version number in the title, they +# cover multiple releases. # The short X.Y version. -version = u'0.1' +version = '' # The full version, including alpha/beta/rc tags. -release = u'0.1' +release = '' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages.