alsatian
alsatian copied to clipboard
Investigate and implement change log
When making new releases people need to know why they should upgrade, having an easy to maintain and read change log will help matters!
Should include roadmap (for future releases)
Title should be same as version
Description should be a markdown formatted list of the issues found against a given milestone
Split by tag to determine what should be included or not or how to display them.
e.g. bugs together, enhancements together, devops ignored
Is there a need for this @jamesrichford? I can't say I've ever read one myself.
It'll become more important the more versions that are published. It's good to be able to track regressions and manage changes but also to highlight improvements and awesome new features :)