Bug 228686 - [NEW PORT] textproc/py-reno: RElease NOtes manager
Summary: [NEW PORT] textproc/py-reno: RElease NOtes manager
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Martin Wilke
URL: https://pypi.org/project/reno/
Keywords:
Depends on:
Blocks: 228690 228701
  Show dependency treegraph
 
Reported: 2018-06-02 14:41 UTC by Kai Knoblich
Modified: 2018-06-02 18:50 UTC (History)
2 users (show)

See Also:


Attachments
py-reno.patch (4.65 KB, patch)
2018-06-02 14:41 UTC, Kai Knoblich
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Knoblich freebsd_committer 2018-06-02 14:41:09 UTC
Created attachment 193925 [details]
py-reno.patch

Hello,

attached is the patch from svn for the Python package textproc/py-reno, 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.

QA:
~~~
- poudriere (11.1-RELEASE amd64 + i386) for each py27 + py36 flavor -> OK
- portlint -> OK
Comment 1 commit-hook freebsd_committer 2018-06-02 18:47:47 UTC
A commit references this bug:

Author: miwi
Date: Sat Jun  2 18:47:07 UTC 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.

Changes:
  head/textproc/Makefile
  head/textproc/py-reno/
  head/textproc/py-reno/Makefile
  head/textproc/py-reno/distinfo
  head/textproc/py-reno/pkg-descr