openCC/changelog
Ran Benita 7460b1aa31 Cherry pick 8.0.2 release notes
(cherry picked from commit e53f79893212391c0bada5f1628b977371a09434)
2024-02-25 00:25:49 +02:00
..
10865.improvement.rst Allow using `warnings.warn()` with Warnings 2024-02-16 13:41:59 +02:00
11311.improvement.rst Consider paths and pathlists relative to cwd in case of an absent ini-file (#11963) 2024-02-14 15:53:28 -03:00
11653.feature.rst New verbosity_test_case ini option (#11653) 2024-02-24 16:27:54 -03:00
11785.trivial.rst fixtures: match fixtures based on actual node hierarchy, not textual nodeids 2024-01-08 21:36:51 +02:00
11790.doc.rst [DOCS] Clarify tmp_path directory location and retention (#11830) 2024-01-18 07:21:49 -03:00
11801.improvement.rst nodes: rename `iterparents()` -> `iter_parents()` 2024-01-14 15:17:41 +02:00
11850.improvement.rst runner: add support for `sys.last_exc` for post-mortem debugging on Python>=3.12 2024-02-23 15:59:32 +02:00
11962.improvement.rst Consider pyproject.toml files for config if no other config files were found (#11962) 2024-02-14 16:08:45 -03:00
11978.improvement.rst Add --log-file-mode option to the logging plugin, enabling appending to log-files (#11979) 2024-02-21 12:02:19 +00:00
12011.bugfix.rst testing: add a regression test for `setup_module` + `--doctest-modules` 2024-02-20 09:36:00 +02:00
12014.bugfix.rst ENH: Improve warning stacklevel (#12014) 2024-02-22 22:11:05 -08:00
README.rst Use hyphenated cmdline options in docs (#11490) 2023-10-10 21:16:24 +00: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 ``--junit-xml``, 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.