Hey folks, I have seen many reviews hitting the queue without reno release notes. Its very simple and straightforward to create a reno release note. Simply run: reno –n blurb This creates a file in the releasenotes directory with a hash. Releasenotes should be committed with the commit in question. Just hand-modify this created releasenote file and everyone’s life is simpler to understand what changed in the final release. Regards -steve -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161223/a90dab48/attachment.html>