Automatically generate the changelog

[kostko]

We should consider automatically generating the changelog.

[nhynes]

running list of generators:

• https://github.com/github-changelog-generator/github-changelog-generator

[ryscheng-mobile]

Our changelog hasnt been updated in months. Seems like this is going to be more relevant post public testnet as we do regular release announcements

[kostko]

Are we planning to make the ekiden repository public once we do a public testnet?

[willscott]

I would guess we won't be there 'at public testnet', but that'll be next next milestone on the way to mainnet

[nhynes]

Another tool https://github.com/NYTimes/Chronicler

[tjanez]

Implementation proposal

Each pull request that is made to the Oasis Core repo should generally include a Changelog fragment in the newsfragments/ directory.

Before a release, all news fragments are automatically assembled into the Changelog file using the towncrier utility and committed into the repo.

Examples of news fragments of (some) popular projects using towncrier:

• pip: https://github.com/pypa/pip/tree/db1a2754bb2aa4f92db781933661c170100f154f/news
• Pipenv: https://github.com/pypa/pipenv/tree/5b6bfc96b5e50011a796ea6c3cc476b7909f38b1/news
• Buildbot: https://github.com/buildbot/buildbot/tree/d2aa5a659305562bc9742afdd03c291fc83e468e/master/buildbot/newsfragments
• Trio: https://github.com/python-trio/trio/tree/master/newsfragments
• Telepresence: https://github.com/telepresenceio/telepresence/tree/bb2eb584cc25deba7e5920938d576693c847bed0/newsfragments

Although it is geared towards Python projects and works with rST by default, it can be made to work with Markdown and for non-Python projects.