Use towncrier to avoid conflicts in HISTORY.rst

[getzze]

See #1138

Documentation here. It is used by many many projects (attrs, pytest, numpy, ...) so it seems a good choice.

Like that, with each commit or PR, we add a news fragment (a file) in the changelog.d folder.
Before making a new release, we call towncrier -- version 2.3.0 and the files are parsed and added nicely to the HISTORY.rst file. They are also deleted from the changelog.d folder.
You can add a news fragment from the command line with: towncrier create --content 'use towncrier' 1138.misc.rst

We have to decide the type of fragments to add. I put:

• breaking
• change
• provider
• refiner
• deprecation
• doc
• misc

With doc and misc showing only the list of PR numbers in the changelog, not the text.

Notice that it will change the formatting of the HISTORY.rst file, now the title for a new release with the date will be on the same line.

I will add the information about how to make a new release in another PR (first handle the conflicts in HISTORY.rst).

[Diaoul]

Cool tool, did not know this one. Out of curiosity, what are alternatives? Why this one and not another?

[ptrcnull]

ooh, I like that! especially since the changelogs are still human-written in the end :P

[getzze]

I didn't check other tools as this one looked great... I found this [talk](https://hynek.me/talks/python-foss/) by the `attrs` author about packaging and I started checking how they do it in `attrs`, `pytest` and `numpy`.

…

On 4 July 2024 09:29:01 GMT+01:00, Antoine Bertin ***@***.***> wrote: Cool tool, did not know this one. Out of curiosity, what are alternatives? Why this one and not another? -- Reply to this email directly or view it on GitHub: #1142 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[github-actions]

Coverage report

This PR does not seem to contain any modification to coverable code.