4 Commits

Author SHA1 Message Date
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
Jay Faulkner
bb3229e72b Update release nodes for Ocata
Updating release notes build to reflect Ocata release.

Change-Id: Idf4b72dcc79baf996eadbfacbe3ff4c1c26fbb13
2017-02-14 10:13:19 -08:00
Jim Rollenhagen
2ba7a9dfb9 Update reno index for Newton
This goes away from our usual style of having a link for the current
series (in this case, Ocata), because it means release team can now do
these updates for us.

Change-Id: I6f6d1838795d4627cdfc404a6ee8c951f4280089
2016-09-22 11:12:07 -04:00
Thierry Carrez
8dc5db45d2 Update reno for stable/mitaka
Change-Id: Ic7b06e374dd20231f5c5b31f9ef3839c4fff9356
2016-03-24 07:31:11 -07:00