Because the stable/ocata branch was created from a commit without a tag,
reno can't figure out where to stop scanning on its own. Give it
instructions to stop scanning at 2.0.0, the earliest Ocata-series
release.
Change-Id: I5df03ab71d438799ac0526c6adb99b7abe3e6ba8
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Releasenote translation publishing is being prepared. 'locale_dirs'
needs to be defined in conf.py to generate translated version of the
release notes.
Note that this repository might not get translated release notes - or
no translations at all - but we add the entry here nevertheless to
prepare for it.
Change-Id: I2ad3ab26a59dfdbdf8d74c5ab577e7820369e232
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
Akihiro Motoki
OpenStack Release Bot