Do not include reno releasenotes in normal documentation
Per the recent release note guidelines for libraries [1],
reno based release notes will be moved out from the normal docs.
The previous (partial) release notes are also moved to
releasenotes directory. The developer documentation now
has a link to the releasenote web site.
In addition, having reno directive in normal sphinx document
prevents users from generating our docs from release tarballs.
Reviewed: https:/ /review. openstack. org/253100 /git.openstack. org/cgit/ openstack/ python- neutronclient/ commit/ ?id=800f35d8a5a 99a67f27b8adf6b 0c5046e748d49a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 800f35d8a5a99a6 7f27b8adf6b0c50 46e748d49a
Author: Akihiro Motoki <email address hidden>
Date: Fri Dec 4 02:25:31 2015 +0900
Do not include reno releasenotes in normal documentation
Per the recent release note guidelines for libraries [1],
reno based release notes will be moved out from the normal docs.
The previous (partial) release notes are also moved to
releasenotes directory. The developer documentation now
has a link to the releasenote web site.
In addition, having reno directive in normal sphinx document
prevents users from generating our docs from release tarballs.
[1] http:// lists.openstack .org/pipermail/ openstack- dev/2015- November/ 080694. html
Change-Id: I817f1a7331b866 4486544c82e1a9a 917864601bf
Closes-Bug: #1520096