No description
Find a file
Jeff Forcier 6c6b0f8850 Cut 1.3.2
2017-10-19 11:16:43 -07:00
docs Cut 1.3.2 2017-10-19 11:16:43 -07:00
integration Shake up output of parse_changelog some more. 2016-10-17 19:38:40 -07:00
releases Cut 1.3.2 2017-10-19 11:16:43 -07:00
tests Update construct_releases() to yield its LineManager too 2016-10-10 11:10:13 -07:00
.gitignore 1st stab at real Sphinx docs hurr 2013-11-11 07:45:41 -08:00
.travis.yml Derp, too used to system package managers 2016-10-10 11:58:51 -07:00
dev-requirements.txt Undo change merged from 1.2 re: invocations compatibility 2017-01-24 10:38:13 -08:00
LICENSE Happy New Year 2017-01-01 12:31:24 -05:00
MANIFEST.in Add MANIFEST.in for LICENSE, etc. Fixes #30 2014-09-04 18:37:44 -07:00
README.rst ==dev is no more 2016-09-15 10:59:58 -07:00
setup.cfg Just needed a little .cfg love re #51 2016-07-25 17:32:12 -07:00
setup.py Re-tighten to avoid backwards incompat sphinx 2017-05-22 10:52:32 -07:00
tasks.py Tweak for new invocations release tasks 2016-12-09 11:18:05 -08:00

.. image:: https://secure.travis-ci.org/bitprophet/releases.png?branch=master
        :target: https://travis-ci.org/bitprophet/releases

What is Releases?
=================

Releases is a Python 2+3 compatible `Sphinx <http://sphinx-doc.org>`_ extension
designed to help you keep a source control friendly, merge friendly changelog
file & turn it into useful, human readable HTML output.

Specifically:

* The source format (kept in your Sphinx tree as ``changelog.rst``) is a
  stream-like timeline that plays well with source control & only requires one
  entry per change (even for changes that exist in multiple release lines).
* The output (when you have the extension installed and run your Sphinx build
  command) is a traditional looking changelog page with a section for every
  release; multi-release issues are copied automatically into each release.
* By default, feature and support issues are only displayed under feature
  releases, and bugs are only displayed under bugfix releases. This can be
  overridden on a per-issue basis.

Some background on why this tool was created can be found in `this blog post
<http://bitprophet.org/blog/2013/09/14/a-better-changelog/>`_.

For more documentation, please see http://releases.readthedocs.io.

.. note::
    You can install the development version via ``pip install -e
    git+https://github.com/bitprophet/releases/#egg=releases``.