(discussion) replace "reno" by "conventional-commits"

[gsemet]

At work we use "commitizen" to generate our changelog, and this required to write commits using "conventional-commits". We loose the ability to "edit" slugs like reno allows us to do, but this makes life simpler. We actually always have to manually edit the release notes, to change some typo, add some intro, ...

If you have better idea on how to generate meaningful release notes ("what changed, what has been fixed, what has been broken"), feel free to use this ticket.

[Davidy22]

I'm not wholly against switching to more automatic tools for release notes, would save a little time per commit, one less thing to ask of contributors too.

[gsemet]

• conventional-commits spec
• enforce conventional commit (check to be added in the pipeline): gitlint
• generate changelog from git history: commitizen

[Davidy22]

I did momentarily try to go by conventional commits but I didn't keep it up, I'm ok with adding CI check for this, automatic instead of having to ask everyone for a slug file.