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: I6158691a389bd8a6c16253284673b3d621907080
tags/0.1.0
Andreas Jaeger 1 year ago
parent
commit
badc30fcf2
1 changed files with 5 additions and 5 deletions
  1. 5
    5
      releasenotes/source/conf.py

+ 5
- 5
releasenotes/source/conf.py View File

@@ -11,8 +11,6 @@
11 11
 # See the License for the specific language governing permissions and
12 12
 # limitations under the License.
13 13
 
14
-from monasca_events_api.version import version_info
15
-
16 14
 # -- General configuration ------------------------------------------------
17 15
 
18 16
 # If your documentation needs a minimal Sphinx version, state it here.
@@ -40,9 +38,11 @@ master_doc = 'index'
40 38
 
41 39
 # General information about the project.
42 40
 repository_name = u'openstack/monasca-events-api'
43
-project = u'Openstack Monitoring Release Notes'
44
-version = version_info.canonical_version_string()
45
-release = version_info.version_string_with_vcs()
41
+project = u'OpenStack Monitoring Release Notes'
42
+# Release notes do not need a version number in the title, they
43
+# cover multiple releases.
44
+version = ''
45
+release = ''
46 46
 bug_project = u'866'
47 47
 bug_tag = u''
48 48
 copyright = u'2014-present, OpenStack Foundation'

Loading…
Cancel
Save