I think it is a good candidate of improvement in reno.
At the moment, the easiest way we can do in neutronclient side is not to include our release notes (release-notes directive) in our documentation and instead point the url http://docs.openstack.org/releasenotes/<project> instead.
Reno (or other tool chains) can be improved to generate release notes during "python setup.py sdist" or similar process
so that the documentation which contains 'releasenotes' sphinx directive can be generated even out of git tree.
I think it is a good candidate of improvement in reno.
At the moment, the easiest way we can do in neutronclient side is not to include our release notes (release-notes directive) in our documentation and instead point the url http:// docs.openstack. org/releasenote s/<project> instead.
Reno (or other tool chains) can be improved to generate release notes during "python setup.py sdist" or similar process
so that the documentation which contains 'releasenotes' sphinx directive can be generated even out of git tree.