releases icon indicating copy to clipboard operation
releases copied to clipboard

A powerful Sphinx changelog-generating extension.

Results 32 releases issues
Sort by recently updated
recently updated
newest added

We are using releases for a number of projects (non-libraries) and often want to label which project a specific issues relates to. Currently this is done like so: `:bug:`DD-200` *(ProjectA)*...

enhancement

After #45 it's become more apparent some things are a bit wonky. The first one that comes to mind is that the major/backported keywords aren't consistent - a 'backported' feature...

enhancement

``` [GABI-PC] Thu 04/28/2016 11:23:09.08 J:\dev\workspace\pythonxy-xy-27\src\python\fabric\__workspace\releases >inv test You indicated pty=True, but your platform doesn't support the 'pty' module! ``` invocations requires pty.

bug

Spinoff of #45. Noticed that e.g. in a situation where one puts out a minor release and major release at the same time, one doesn't actually want features in the...

enhancement

Right now logging is scattershot and uses ye olde local `sys.stderr.write` functionality, with bonus "rebind to a partial within functions due to requirement of access to `app.config` to tell whether...

enhancement

Right now the test suite is largely hand-made, semi-internal data structures, plus various wrappers tying them into real-enough structures that the top level API calls can work with. So e.g....

enhancement

Leftover from #45. There's a skeleton test for this and possibly an artifact in the docs.

enhancement

You can currently add multi-line entries/notes beyond the basic description for features and bugs. (see [Release changelog](https://releases.readthedocs.org/en/latest/changelog.html#0.3.0), `feature #1`). Is it possible to add similar notes to the release entry...

enhancement

Support items occupy a strange spot between feature and bug; when backported, they frequently don't need to appear in 'next feature release' territory (or, indeed, the actual feature release when...

Attempt to detect whether a Sphinx build ran 100% without mutating a changelog, and bail out with a useful error. When this is not done, the only telltale sign is...