Open Stack

Folks,

We are now using reno[1] for release notes in trove, trove-dashboard,
and python-troveclient.

If you submit a change to any one of these repositories, that is going
to be visible to a user (i.e. not changes that only impact tests, or are
procedural changes relating to management of the repository etc.,)
please DO add a release note.

For instructions on how to add a release note, please see [2].

Once you add a release note, please be sure to run

	tox -e releasenotes 

before you push your change set for review. It will save you a lot of
time, and will spare the CI a lot of unnecessary testing.

If you are fixing a bug, please include the LP bug number(s) in the
release note.

Some samples of release notes are provided in [3], [4], and [5].

Thanks,

-amrith

[1] http://docs.openstack.org/developer/reno/
[2]
http://docs.openstack.org/project-team-guide/release-management.html#how-to-add-new-release-notes
[3]
https://review.openstack.org/#/c/237184/6/releasenotes/notes/fix-cluster-issues-2651eaf31a85b11f.yaml
[4]
https://review.openstack.org/#/c/300009/4/releasenotes/notes/fix-mysql-replication-bf2b131994a5a772.yaml
[5]
https://review.openstack.org/#/c/301936/4/releasenotes/notes/locality-support-for-clusters-78bb74145d867df2.yaml

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: This is a digitally signed message part
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160416/5e9be912/attachment.pgp>