test_ok2/changelog
Bruno Oliveira b95991aeea
Merge pull request #7960 from nicoddemus/cherry-pick-release
Merge pull request #7958 from pytest-dev/release-6.1.2
2020-10-28 14:36:37 -03:00
..
4824.bugfix.rst fixtures: fix quadratic behavior in the number of autouse fixtures 2020-10-25 00:49:23 +03:00
7425.feature.rst New pytester fixture (#7854) 2020-10-12 12:13:06 -03:00
7710.improvement.rst python_api: let approx() take nonnumeric values (#7710) 2020-09-28 12:17:23 -03:00
7758.bugfix.rst cacheprovider: fix some files in packages getting lost from --lf 2020-10-19 19:02:43 +03:00
7780.doc.rst doc: patch Sphinx to detect our `@final` for marking classes as `final` 2020-10-03 13:13:14 +03:00
7802.trivial.rst Bump attrs requirement from >=17.4.0 to >=19.2.0 2020-09-27 13:17:59 +03:00
7808.breaking.rst py36+: drop python3.5 in CI and setup.cfg 2020-10-02 14:00:11 -07:00
7872.doc.rst Added changelog/7872.doc.rst 2020-10-07 18:06:13 -04:00
7878.doc.rst ask for commit after changelog and authors file edit (#7878) 2020-10-09 16:10:54 +02:00
7911.bugfix.rst Increase temp dir deletion period to 3 days (#7914) 2020-10-28 08:23:35 -03:00
7913.bugfix.rst pytester: workaround issue causing spawn to crash or hang 2020-10-25 16:31:47 +02:00
README.rst docs: use doc/en/_build/html for html output (#6842) 2020-02-29 00:47:30 +01:00
_template.rst Update CHANGELOG template to put issue links at the start of entries 2018-07-07 11:02:33 -03:00

README.rst

This directory contains "newsfragments" which are short files that contain a small **ReST**-formatted
text that will be added to the next ``CHANGELOG``.

The ``CHANGELOG`` will be read by **users**, so this description should be aimed to pytest users
instead of describing internal changes which are only relevant to the developers.

Make sure to use full sentences in the **past or present tense** and use punctuation, examples::

    Improved verbose diff output with sequences.

    Terminal summary statistics now use multiple colors.

Each file should be named like ``<ISSUE>.<TYPE>.rst``, where
``<ISSUE>`` is an issue number, and ``<TYPE>`` is one of:

* ``feature``: new user facing features, like new command-line options and new behavior.
* ``improvement``: improvement of existing functionality, usually without requiring user intervention (for example, new fields being written in ``--junitxml``, improved colors in terminal, etc).
* ``bugfix``: fixes a bug.
* ``doc``: documentation improvement, like rewording an entire session or adding missing docs.
* ``deprecation``: feature deprecation.
* ``breaking``: a change which may break existing suites, such as feature removal or behavior change.
* ``vendor``: changes in packages vendored in pytest.
* ``trivial``: fixing a small typo or internal change that might be noteworthy.

So for example: ``123.feature.rst``, ``456.bugfix.rst``.

If your PR fixes an issue, use that number here. If there is no issue,
then after you submit the PR and get the PR number you can add a
changelog using that instead.

If you are not sure what issue type to use, don't hesitate to ask in your PR.

``towncrier`` preserves multiple paragraphs and formatting (code blocks, lists, and so on), but for entries
other than ``features`` it is usually better to stick to a single paragraph to keep it concise.

You can also run ``tox -e docs`` to build the documentation
with the draft changelog (``doc/en/_build/html/changelog.html``) if you want to get a preview of how your change will look in the final release notes.