Browse Source

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: I0919ad158b4d8cae993f5fd137d4759402d0851c
Andreas Jaeger 1 year ago
parent
commit
c70ab43107
1 changed files with 4 additions and 7 deletions
  1. 4
    7
      releasenotes/source/conf.py

+ 4
- 7
releasenotes/source/conf.py View File

@@ -19,7 +19,6 @@
19 19
 # import os
20 20
 # import sys
21 21
 # sys.path.insert(0, os.path.abspath('.'))
22
-from kuryr.lib import version as kuryr_version
23 22
 
24 23
 # -- General configuration ------------------------------------------------
25 24
 
@@ -61,14 +60,12 @@ bug_project = 'kuryr'
61 60
 bug_tag = ''
62 61
 html_last_updated_fmt = '%Y-%m-%d %H:%M'
63 62
 
64
-# The version info for the project you're documenting, acts as replacement for
65
-# |version| and |release|, also used in various other places throughout the
66
-# built documents.
67
-#
63
+# Release notes do not need a version number in the title, they
64
+# cover multiple releases.
68 65
 # The short X.Y version.
69
-version = kuryr_version.version_info.release_string()
66
+version = ''
70 67
 # The full version, including alpha/beta/rc tags.
71
-release = kuryr_version.version_info.version_string()
68
+release = ''
72 69
 
73 70
 # The language for content autogenerated by Sphinx. Refer to documentation
74 71
 # for a list of supported languages.

Loading…
Cancel
Save