8 Commits

Author SHA1 Message Date
f7c208084c Update reno for stable/rocky
Change-Id: I6f14d42362fc2364d967b0e2a4ebc57700fab200
2018-09-04 16:24:24 +00:00
e2d3119bd6 Update reno for stable/queens
Change-Id: I8ee8b4198ccf2f79fdc1acc3a303ede18960a2a1
2018-03-01 16:51:56 +00:00
6155ea595a Update reno for stable/pike
Change-Id: I92fed4875a5a93c46a3e58c62e5df58180d0f0d1
2017-09-05 13:11:17 +00:00
09a0cc80c3 Update reno for stable/ocata
Change-Id: I99f2932fb74b399a93b3c6547b8d62a595ce6ce6
2017-02-15 17:36:36 +00:00
Jeffrey Zhang
9ccdcd5028 Remove non-existent branches in releasenote
There is no liberty, mitaka and newton branch in kolla-ansible project.

Change-Id: I6d1ecaaea4382050bab3a8130667759bbcde3e91
2016-11-18 00:00:58 +08:00
Davanum Srinivas
0613c4114c Update reno for stable/newton
Change-Id: I1d374efb49b6d50b95641278376b21a61e054924
2016-10-13 09:28:41 -04:00
Lu lei
b2ad476a86 Update the order of release note page
In order to support automatically updating the release notes when we
create stable branches, we want the pages to be in a standard order.
This patch updates the order to be reverse chronological, so the most
recent notes appear at the top.

TrivialFix.

Change-Id: I8eca97a75f8c6ee1f41712678b12b7e9dac655dd
2016-09-22 17:38:05 +08:00
Steven Dake
801ef2e843 Add reno support
For proper release note generation on the releases.openstack.org
website, this change will need to be backported into mitaka and
liberty as well.  Then a special one-file reno file will have to
be added for mitaka describing the features and the same story
for liberty.

See log of the discussion here:
http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2016-03-23.log.html#t2016-03-23T18:00:05

Change-Id: I3c298ae08ec4645f384ea5829cb0851fe82f4557
Partially-Implements: blueprint add-reno
2016-03-23 11:59:35 -07:00