Skip to content

Commit dc7eb62

Browse files
committed
docs: Don't version links to reno docs
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 <[email protected]> (cherry picked from commit 8b9dad0)
1 parent 498608c commit dc7eb62

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

doc/source/conf.py

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -135,10 +135,8 @@
135135

136136
# keep this ordered to keep mriedem happy
137137
#
138-
# NOTE(kchamart): Versioned TripleO Docs is not a yet a "thing". Remove
139-
# this note when they can be versioned, and add 'tripleo-docs' to the
140-
# set of projects below.
141-
138+
# NOTE(stephenfin): Projects that don't have a release branch, like TripleO and
139+
# reno, should not be included here
142140
openstack_projects = [
143141
'ceilometer',
144142
'cinder',
@@ -155,7 +153,6 @@
155153
'placement',
156154
'python-novaclient',
157155
'python-openstackclient',
158-
'reno',
159156
'watcher',
160157
]
161158
# -- Custom extensions --------------------------------------------------------

doc/source/contributor/releasenotes.rst

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,10 @@ Release Notes
66
What is reno ?
77
--------------
88

9-
Nova uses :reno-doc:`reno <>` for providing release notes in-tree. That means
10-
that a patch can include a *reno file* or a series can have a follow-on change
11-
containing that file explaining what the impact is.
9+
Nova uses `reno <https://docs.openstack.org/reno/latest/>`__ for providing
10+
release notes in-tree. That means that a patch can include a *reno file* or a
11+
series can have a follow-on change containing that file explaining what the
12+
impact is.
1213

1314
A *reno file* is a YAML file written in the ``releasenotes/notes`` tree which
1415
is generated using the *reno* tool this way:
@@ -20,7 +21,9 @@ is generated using the *reno* tool this way:
2021
where usually ``<name-your-file>`` can be ``bp-<blueprint_name>`` for a
2122
blueprint or ``bug-XXXXXX`` for a bugfix.
2223

23-
Refer to the :reno-doc:`reno documentation <user/index.html>` for more information.
24+
Refer to the `reno documentation
25+
<https://docs.openstack.org/reno/latest/user/index.html>`__ for more
26+
information.
2427

2528

2629
When a release note is needed

0 commit comments

Comments
 (0)