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
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
