From owner-svn-ports-all@freebsd.org Sat Jun 2 18:47:09 2018 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9B38FD23C5; Sat, 2 Jun 2018 18:47:08 +0000 (UTC) (envelope-from miwi@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2672071B77; Sat, 2 Jun 2018 18:47:08 +0000 (UTC) (envelope-from miwi@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 0810F139FB; Sat, 2 Jun 2018 18:47:08 +0000 (UTC) (envelope-from miwi@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w52Il7Lv018837; Sat, 2 Jun 2018 18:47:07 GMT (envelope-from miwi@FreeBSD.org) Received: (from miwi@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w52Il7Oo018834; Sat, 2 Jun 2018 18:47:07 GMT (envelope-from miwi@FreeBSD.org) Message-Id: <201806021847.w52Il7Oo018834@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: miwi set sender to miwi@FreeBSD.org using -f From: Martin Wilke Date: Sat, 2 Jun 2018 18:47:07 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r471392 - in head/textproc: . py-reno X-SVN-Group: ports-head X-SVN-Commit-Author: miwi X-SVN-Commit-Paths: in head/textproc: . py-reno X-SVN-Commit-Revision: 471392 X-SVN-Commit-Repository: ports MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jun 2018 18:47:09 -0000 Author: miwi Date: Sat Jun 2 18:47:06 2018 New Revision: 471392 URL: https://svnweb.freebsd.org/changeset/ports/471392 Log: 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. Added: head/textproc/py-reno/ head/textproc/py-reno/Makefile (contents, props changed) head/textproc/py-reno/distinfo (contents, props changed) head/textproc/py-reno/pkg-descr (contents, props changed) Modified: head/textproc/Makefile Modified: head/textproc/Makefile ============================================================================== --- head/textproc/Makefile Sat Jun 2 18:45:34 2018 (r471391) +++ head/textproc/Makefile Sat Jun 2 18:47:06 2018 (r471392) @@ -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 Added: head/textproc/py-reno/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/textproc/py-reno/Makefile Sat Jun 2 18:47:06 2018 (r471392) @@ -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 Added: head/textproc/py-reno/distinfo ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/textproc/py-reno/distinfo Sat Jun 2 18:47:06 2018 (r471392) @@ -0,0 +1,3 @@ +TIMESTAMP = 1527350434 +SHA256 (reno-2.9.2.tar.gz) = 7b720b64a9c9dcec0ab252af3e0551b971a83ec4ebca9ee513e98fb2820f2426 +SIZE (reno-2.9.2.tar.gz) = 81244 Added: head/textproc/py-reno/pkg-descr ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/textproc/py-reno/pkg-descr Sat Jun 2 18:47:06 2018 (r471392) @@ -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/