=========================================
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
=================
.. .. image:: https://governance.openstack.org/tc/badges/reno.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
* Free software: Apache license
* Documentation: https://docs.openstack.org/reno/latest/
* Source: https://opendev.org/openstack/reno/
* Bugs: https://storyboard.openstack.org/#!/project/933
* IRC: #openstack-release on OFTC
Raw data
{
"_id": null,
"home_page": "https://docs.openstack.org/reno/latest/",
"name": "reno",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.6",
"maintainer_email": "",
"keywords": "",
"author": "OpenStack",
"author_email": "openstack-discuss@lists.openstack.org",
"download_url": "https://files.pythonhosted.org/packages/9b/a0/a2526ccefaf41717f7387fb5c068a094af0f5853822eb43c792e338d9e0b/reno-4.1.0.tar.gz",
"platform": null,
"description": "=========================================\n reno: A New Way to Manage Release Notes\n=========================================\n\nReno is a release notes manager designed with high throughput in mind,\nsupporting fast distributed development teams without introducing\nadditional development processes. Our goal is to encourage detailed\nand accurate release notes for every release.\n\nReno uses git to store its data, along side the code being\ndescribed. This means release notes can be written when the code\nchanges are fresh, so no details are forgotten. It also means that\nrelease notes can go through the same review process used for managing\ncode and other documentation changes.\n\nReno stores each release note in a separate file to enable a large\nnumber of developers to work on multiple patches simultaneously, all\ntargeting the same branch, without worrying about merge\nconflicts. This cuts down on the need to rebase or otherwise manually\nresolve conflicts, and keeps a development team moving quickly.\n\nReno also supports multiple branches, allowing release notes to be\nback-ported from master to maintenance branches together with the\ncode for bug fixes.\n\nReno organizes notes into logical groups based on whether they\ndescribe new features, bug fixes, known issues, or other topics of\ninterest to the user. Contributors categorize individual notes as they\nare added, and reno combines them before publishing.\n\nNotes can be styled using reStructuredText directives, and reno's\nSphinx integration makes it easy to incorporate release notes into\nautomated documentation builds.\n\nNotes are automatically associated with the release version based on\nthe git tags applied to the repository, so it is not necessary to\ntrack changes manually using a bug tracker or other tool, or to worry\nthat an important change will be missed when the release notes are\nwritten by hand all at one time, just before a release.\n\nModifications to notes are incorporated when the notes are shown in\ntheir original location in the history. This feature makes it possible\nto correct typos or otherwise fix a published release note after a\nrelease is made, but have the new note content associated with the\noriginal version number. Notes also can be deleted, eliminating them\nfrom future documentation builds.\n\nProject Meta-data\n=================\n\n.. .. image:: https://governance.openstack.org/tc/badges/reno.svg\n :target: https://governance.openstack.org/tc/reference/tags/index.html\n\n* Free software: Apache license\n* Documentation: https://docs.openstack.org/reno/latest/\n* Source: https://opendev.org/openstack/reno/\n* Bugs: https://storyboard.openstack.org/#!/project/933\n* IRC: #openstack-release on OFTC\n\n\n\n",
"bugtrack_url": null,
"license": "",
"summary": "RElease NOtes manager",
"version": "4.1.0",
"project_urls": {
"Homepage": "https://docs.openstack.org/reno/latest/"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "bd4fe933aae43bfaea4f6646009379036bec42d78ee2231ab9a983317c3a1c4b",
"md5": "9a99b6f491e4e245749bd5a29c9f2d12",
"sha256": "9b6a2cb768ffb7f7c74bbd76822acff70840a1219f45bcec5080dbc108df4f96"
},
"downloads": -1,
"filename": "reno-4.1.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "9a99b6f491e4e245749bd5a29c9f2d12",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.6",
"size": 72126,
"upload_time": "2024-03-04T07:40:33",
"upload_time_iso_8601": "2024-03-04T07:40:33.517418Z",
"url": "https://files.pythonhosted.org/packages/bd/4f/e933aae43bfaea4f6646009379036bec42d78ee2231ab9a983317c3a1c4b/reno-4.1.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "9ba0a2526ccefaf41717f7387fb5c068a094af0f5853822eb43c792e338d9e0b",
"md5": "765a468a3ba485747504d7a3a6e78604",
"sha256": "f992f1fdbd16215ec9de47af08131d53a2830c9e78439eb563ce8d6a7f625370"
},
"downloads": -1,
"filename": "reno-4.1.0.tar.gz",
"has_sig": false,
"md5_digest": "765a468a3ba485747504d7a3a6e78604",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6",
"size": 86657,
"upload_time": "2024-03-04T07:40:35",
"upload_time_iso_8601": "2024-03-04T07:40:35.552210Z",
"url": "https://files.pythonhosted.org/packages/9b/a0/a2526ccefaf41717f7387fb5c068a094af0f5853822eb43c792e338d9e0b/reno-4.1.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-03-04 07:40:35",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "reno"
}
JSON