Commit Graph

4 Commits (17d6123f789fd6522bcdb3ef215f8688f073f505)

Author SHA1 Message Date
OpenStack Release Bot fd62949c6e Update reno for stable/ocata
Change-Id: I2eec54f59511b8005c2d57326cca45dac51db900
2017-02-04 01:03:26 +00:00
Davanum Srinivas 949d244f52 Update reno for stable/newton
Change-Id: I3c8f0662f252732fe839a144e548c158117e9a07
2016-09-15 09:17:49 -04:00
Andreas Jaeger 5eaa96f638 Fix releasenotes
There's no stable/liberty branch, remove the file so that release notes
building works.

Note: This is needed to fix translation sync, see
http://logs.openstack.org/44/44654d5dd07104d6bda7bad24eaa8742c19697ec/post/networking-ovn-upstream-translation-update/d11ccac/

Change-Id: I8caa3a155eb1a412c9c8ad85bb3a60d3e6a25fe0
2016-04-18 19:58:22 +02:00
Gary Kotton 18fd7a1a1e Add reno for release notes management
Release management team has modified the way it releases
projects and a new process and guideline has been established.
This change adds support for the same. More information on
this can be found at [1].

Within OpenStack, reno can be used to create release notes
using the following command:
tox -e venv -- reno new slug-goes-here
where slug-goes-here is a prefix to your notes.
More info on reno usage can be found at [2].

[1]: http://lists.openstack.org/pipermail/openstack-dev/2015-November/078301.html
[2]: http://docs.openstack.org/developer/reno/usage.html

Change-Id: Iad4573a738dcc972b003c20b1a3895dfd3094c2b
2015-12-06 07:04:50 -08:00