openstack/nova
Code Issues Proposed changes

docs: Don't version links to reno docs

Browse Source 
reno doesn't have stable branches and doesn't version its documentation.
There's no point versioning our links to same.

Change-Id: Id782d3b11715bc3211e7952fb01b42a659d06e36
Closes-Bug: #1830926
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This commit is contained in:
Stephen Finucane 2019-05-29 13:39:06 +01:00 committed by Stephen Finucane
parent d4f58f5eb6
commit 8b9dad0b63
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/conf.py
View File

@ -134,10 +134,8 @@ latex_documents = [
# keep this ordered to keep mriedem happy
#
# NOTE(kchamart): Versioned TripleO Docs is not a yet a "thing". Remove
# this note when they can be versioned, and add 'tripleo-docs' to the
# set of projects below.
# NOTE(stephenfin): Projects that don't have a release branch, like TripleO and
# reno, should not be included here
openstack_projects = [
'ceilometer',
'cinder',
@ -154,7 +152,6 @@ openstack_projects = [
'placement',
'python-novaclient',
'python-openstackclient',
'reno',
'watcher',
]
# -- Custom extensions --------------------------------------------------------

11
doc/source/contributor/releasenotes.rst
View File

@ -6,9 +6,10 @@ Release Notes
What is reno ?
--------------
Nova uses :reno-doc:`reno <>` for providing release notes in-tree. That means
that a patch can include a *reno file* or a series can have a follow-on change
containing that file explaining what the impact is.
Nova uses `reno <https://docs.openstack.org/reno/latest/>`__ for providing
release notes in-tree. That means that a patch can include a *reno file* or a
series can have a follow-on change containing that file explaining what the
impact is.
A *reno file* is a YAML file written in the ``releasenotes/notes`` tree which
is generated using the *reno* tool this way:
@ -20,7 +21,9 @@ is generated using the *reno* tool this way:
where usually ``<name-your-file>`` can be ``bp-<blueprint_name>`` for a
blueprint or ``bug-XXXXXX`` for a bugfix.
Refer to the :reno-doc:`reno documentation <user/index.html>` for more information.
Refer to the `reno documentation
<https://docs.openstack.org/reno/latest/user/index.html>`__ for more
information.
When a release note is needed