py-libp2p/newsfragments
2019-11-27 10:38:08 -08:00
..
350.bugfix.rst Back-generate release notes for v0.1.3 release 2019-11-27 10:38:08 -08:00
353.internal.rst Back-generate release notes for v0.1.3 release 2019-11-27 10:38:08 -08:00
354.bugfix.rst Back-generate release notes for v0.1.3 release 2019-11-27 10:38:08 -08:00
355.bugfix.rst Back-generate release notes for v0.1.3 release 2019-11-27 10:38:08 -08:00
356.internal.rst Back-generate release notes for v0.1.3 release 2019-11-27 10:38:08 -08:00
357.misc.rst Back-generate release notes for v0.1.3 release 2019-11-27 10:38:08 -08:00
README.md Add internal type for release notes 2019-11-25 21:44:29 +01:00
validate_files.py Add internal type for release notes 2019-11-25 21:44:29 +01:00

This directory collects "newsfragments": short files that each contain a snippet of ReST-formatted text that will be added to the next release notes. This should be a description of aspects of the change (if any) that are relevant to users. (This contrasts with the commit message and PR description, which are a description of the change as relevant to people working on the code itself.)

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

  • feature
  • bugfix
  • performance
  • doc
  • internal
  • removal
  • misc

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

If the PR fixes an issue, use that number here. If there is no issue, then open up the PR first and use the PR number for the newsfragment.

Note that the towncrier tool will automatically reflow your text, so don't try to do any fancy formatting. Run towncrier --draft to get a preview of what the release notes entry will look like in the final release notes.