-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate and implement change log #70
Comments
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 :) |
When making new releases people need to know why they should upgrade, having an easy to maintain and read change log will help matters!
The text was updated successfully, but these errors were encountered: