From f533f42ca634b471d72ed49f59775f07c811a2c6 Mon Sep 17 00:00:00 2001 From: Mark Goddard Date: Thu, 26 Sep 2019 14:41:26 +0100 Subject: [PATCH] Remove earliest version from releasing docs, update examples The bug in reno is now fixed. Change-Id: I803ec65157fce93a453b2b994e117a542aaad847 --- doc/source/contributor/releasing.rst | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/doc/source/contributor/releasing.rst b/doc/source/contributor/releasing.rst index 17372a2730..79924d6663 100644 --- a/doc/source/contributor/releasing.rst +++ b/doc/source/contributor/releasing.rst @@ -157,16 +157,14 @@ This includes: * updating the release notes RST to include the new branch. The generated RST does not include the version range in the title, so we - typically submit a follow-up patch to do that. We also manually mark - the ``earliest-version`` directive on the new page, due to a `reno bug - ` that may cause this to - be incorrect for stable branches. + typically submit a follow-up patch to do that. An example of this patch is + `here `__. We need to submit patches for changes in the stable branch to: * update the ironic devstack plugin to point at the branched tarball for IPA. An example of this patch is - `here `_. + `here `_. * update links in the documentation (``ironic/doc/source/``) to point to the branched versions of any openstack projects' (that branch) documents. As of Pike release, the only outlier is