From dac6f829af0fcca3586d7e953c7020692ae700c0 Mon Sep 17 00:00:00 2001 From: Stephen Finucane Date: Mon, 24 Sep 2018 11:58:46 +0100 Subject: docs: Add docs for reno integration Change-Id: I9a77a4f6397464c33181d8b4bd2a9ae79c058b47 Signed-off-by: Stephen Finucane --- doc/source/user/features.rst | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) (limited to 'doc/source/user/features.rst') diff --git a/doc/source/user/features.rst b/doc/source/user/features.rst index dfbc18b..80339df 100644 --- a/doc/source/user/features.rst +++ b/doc/source/user/features.rst @@ -62,7 +62,7 @@ From this, we note a couple of the main features of *pbr*: - Extensive use of ``setup.cfg`` for configuration - Automatic package metadata generation (``version``) - Automatic metadata file generation (``AUTHOR``, ``ChangeLog``, - ``MANIFEST.in``) + ``MANIFEST.in``, ``RELEASENOTES.txt``) In addition, there are other things that you don't see here but which *pbr* will do for you: @@ -253,6 +253,21 @@ test files. __ https://packaging.python.org/tutorials/distributing-packages/#manifest-in +Release Notes +~~~~~~~~~~~~~ + +.. admonition:: Summary + + *pbr* will automatically use *reno* \'s ``build_reno`` setuptools command + to generate a release notes file, if reno is available and configured. + +If using *reno*, you may wish to include a copy of the release notes in your +packages. *reno* provides a ``build_reno`` `setuptools command`__ and, if reno +is present and configured, *pbr* will automatically call this to generate a +release notes file for inclusion in your package. + +__ https://docs.openstack.org/reno/latest/user/setuptools.html + Setup Commands -------------- -- cgit v1.2.1