ironic/releasenotes/source
Jim Rollenhagen 3b8c3879a5 Explicitly mark earliest-version for release notes
This uses reno's `earliest-version` directive to explicitly point out
where the release notes for a given branch should begin. There is a bug
in reno when dealing with stable branches, where it does not always find
the correct version to begin with.

It also updates our release docs to indicate we should continue marking
this. This step can be removed when the reno bug is fixed, though it
doesn't hurt to continue marking this explicitly.

Change-Id: I6502ff95a52c2c855356e9875291f27ec44e7ffa
Related-Bug: #1746076
2018-01-29 14:15:01 -05:00
..
_static Add reno for release notes management 2015-11-13 03:22:32 -08:00
_templates Add reno for release notes management 2015-11-13 03:22:32 -08:00
conf.py Remove setting of version/release from releasenotes 2017-11-17 10:13:05 +01:00
index.rst Update reno for stable/pike 2017-08-17 14:31:17 +00:00
liberty.rst Explicitly mark earliest-version for release notes 2018-01-29 14:15:01 -05:00
mitaka.rst Explicitly mark earliest-version for release notes 2018-01-29 14:15:01 -05:00
newton.rst Explicitly mark earliest-version for release notes 2018-01-29 14:15:01 -05:00
ocata.rst Explicitly mark earliest-version for release notes 2018-01-29 14:15:01 -05:00
pike.rst Explicitly mark earliest-version for release notes 2018-01-29 14:15:01 -05:00
unreleased.rst remove explicit directions for release notes on current branch 2017-05-24 15:43:37 -04:00