Reno is a release notes manager designed with high throughput in mind,

supporting fast distributed development teams without introducing additional
development processes. The 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.

WWW: https://docs.openstack.org/reno/

PR:		228686
Submitted by:	freebsd_ports@k-worx.org
Sponsored by:	iXsystems Inc.
This commit is contained in:
Martin Wilke 2018-06-02 18:47:06 +00:00
parent 999a178e46
commit 5b02b710fe
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=471392
4 changed files with 53 additions and 0 deletions

View file

@ -1371,6 +1371,7 @@
SUBDIR += py-qt5-xmlpatterns
SUBDIR += py-rdflib
SUBDIR += py-regex
SUBDIR += py-reno
SUBDIR += py-reverend
SUBDIR += py-rnc2rng
SUBDIR += py-rss2gen

29
textproc/py-reno/Makefile Normal file
View file

@ -0,0 +1,29 @@
# $FreeBSD$
PORTNAME= reno
DISTVERSION= 2.9.2
CATEGORIES= textproc python
MASTER_SITES= CHEESESHOP
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
MAINTAINER= freebsd_ports@k-worx.org
COMMENT= RElease NOtes manager
LICENSE= APACHE20
LICENSE_FILE= ${WRKSRC}/LICENSE
BUILD_DEPENDS= ${PYTHON_PKGNAMEPREFIX}pbr>0:devel/py-pbr@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}six>=1.9.0:devel/py-six@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}yaml>=3.1.0:devel/py-yaml@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}dulwich>=0.15.0:devel/dulwich@${PY_FLAVOR}
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}pbr>0:devel/py-pbr@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}yaml>=3.1.0:devel/py-yaml@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}six>=1.9.0:devel/py-six@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}dulwich>=0.15.0:devel/dulwich@${PY_FLAVOR}
USES= python
USE_PYTHON= distutils concurrent autoplist
NO_ARCH= yes
.include <bsd.port.mk>

View file

@ -0,0 +1,3 @@
TIMESTAMP = 1527350434
SHA256 (reno-2.9.2.tar.gz) = 7b720b64a9c9dcec0ab252af3e0551b971a83ec4ebca9ee513e98fb2820f2426
SIZE (reno-2.9.2.tar.gz) = 81244

View file

@ -0,0 +1,20 @@
Reno is a release notes manager designed with high throughput in mind,
supporting fast distributed development teams without introducing additional
development processes. The 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.
WWW: https://docs.openstack.org/reno/