trove need to add releasenote

[jian.song]

When some of our patches changed the way the user was using, or did something, or modified some of the bugs change the user using. We need to add releasenote to ensure that the content will be available at the time of the release. Here will be the recent merge I think the need to add releasenote patch summed up, I hope each patch the author to add releasenote as soon as possible.
If have bug number to write it in the relasenote inside, If do not have it there is best to write review the connection (I think this helps to quickly find)

Q1-Q2:
[1]:https://review.openstack.org/#/c/513276/
[2]:https://review.openstack.org/#/c/493563/
[3]:https://review.openstack.org/#/c/518639/
[4]:https://review.openstack.org/#/c/507428/
[5]:https://review.openstack.org/#/c/410348/
[6]:https://review.openstack.org/#/c/420819/
[7]:https://review.openstack.org/#/c/493775/

PIKE-Q1:
[1]:https://review.openstack.org/#/c/81410/

The basis of these is:
1. Change the way users use trove (such as new parameter support, parameter content limit)
2. changed the user's trove habits (with the previous version)

This is my current idea, from PIKE to Q2 before the release, patch is not a lot, so we can continue to add according to our ideas which need to increase the releasenote patch. thanks for everyone support.

releasenote information:https://docs.openstack.org/reno/latest/

[jian.song (jiansong)]

Hi Manoj, is melissaml to add all releasenote?