openstack
/
blazar
Code Issues Proposed changes

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: Ic39597b2190bc747f6d9a97221b172cbfc8c89fa
This commit is contained in:
rajat29 2017-11-17 10:33:04 +05:30
parent 9a08d37e5c
commit 0da6818296
1 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
releasenotes/source/conf.py
View File

@ -61,15 +61,11 @@ master_doc = 'index'
project = u'Blazar Release Notes'
copyright = u'2017, Blazar developers'
# 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.
#
from blazar.version import version_info as blazar_version
# Release notes are version independent.
# The short X.Y version.
version = blazar_version.canonical_version_string()
version = ''
# The full version, including alpha/beta/rc tags.
release = blazar_version.version_string_with_vcs()
release = ''
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.