openstack
/
reno
Code Issues Proposed changes
Release notes management tool
275 Commits 2 Branches 53 Tags 2.6 MiB
Python 100%
Go to file
Doug Hellmann 9d058ae097 add release note for scanner fix 
See I4e41c482695e93ebb5a73866c432636201a7534f for the code change.

Change-Id: Ia881488d459cd9b86f73986b016ff9f1eff50699
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
 		2017-11-15 16:02:37 -05:00
doc/source update bindep list 2017-11-15 14:25:34 -05:00
examples/notes expand examples in documentation 2017-06-06 17:07:08 -04:00
releasenotes/notes add release note for scanner fix 2017-11-15 16:02:37 -05:00
reno remove some duplication in ChangeTracker 2017-11-09 20:11:07 +11:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:55:10 +00:00
.gitignore ignore all coverage output files 2016-06-22 13:47:59 -04:00
.gitreview Initial Cookiecutter Commit. 2015-08-26 20:04:56 +00:00
.mailmap Initial Cookiecutter Commit. 2015-08-26 20:04:56 +00:00
.testr.conf Initial Cookiecutter Commit. 2015-08-26 20:04:56 +00:00
CONTRIBUTING.rst Clean up rendered HTML with openstackdocstheme 2017-07-19 09:44:08 +00:00
HACKING.rst Replace http with https 2017-06-19 08:59:07 +08:00
LICENSE Initial Cookiecutter Commit. 2015-08-26 20:04:56 +00:00
MANIFEST.in Initial Cookiecutter Commit. 2015-08-26 20:04:56 +00:00
README.rst Update documention link for doc migration 2017-07-13 15:22:28 +00:00
bindep.txt update bindep list 2017-11-15 14:25:34 -05:00
requirements.txt requirements: Stop requiring a specific pbr version 2017-08-24 12:03:25 +01:00
setup.cfg Update documention link for doc migration 2017-07-13 15:22:28 +00:00
setup.py Initial Cookiecutter Commit. 2015-08-26 20:04:56 +00:00
test-requirements.txt switch from oslosphinx to openstackdocstheme 2017-06-28 14:46:09 -04:00
tox.ini add a lint command 2017-05-03 15:53:44 -04:00

README.rst

reno: A New Way to Manage Release Notes

Reno is a release notes manager designed with high throughput in mind, supporting fast distributed development teams without introducing additional development processes. Our goal is to encourage detailed and accurate release notes for every release.

Reno uses git to store its data, along side the code being described. This means release notes can be written when the code changes are fresh, so no details are forgotten. It also means that release notes can go through the same review process used for managing code and other documentation changes.

Reno stores each release note in a separate file to enable a large number of developers to work on multiple patches simultaneously, all targeting the same branch, without worrying about merge conflicts. This cuts down on the need to rebase or otherwise manually resolve conflicts, and keeps a development team moving quickly.

Reno also supports multiple branches, allowing release notes to be back-ported from master to maintenance branches together with the code for bug fixes.

Reno organizes notes into logical groups based on whether they describe new features, bug fixes, known issues, or other topics of interest to the user. Contributors categorize individual notes as they are added, and reno combines them before publishing.

Notes can be styled using reStructuredText directives, and reno's Sphinx integration makes it easy to incorporate release notes into automated documentation builds.

Notes are automatically associated with the release version based on the git tags applied to the repository, so it is not necessary to track changes manually using a bug tracker or other tool, or to worry that an important change will be missed when the release notes are written by hand all at one time, just before a release.

Modifications to notes are incorporated when the notes are shown in their original location in the history. This feature makes it possible to correct typos or otherwise fix a published release note after a release is made, but have the new note content associated with the original version number. Notes also can be deleted, eliminating them from future documentation builds.

Project Meta-data