Re:Generate Your Changelog From GitHub Issues
by skywinder on Friday March 20, 2015 @07:39PM
(#9241310)
> We don't need fine-grained details of every internal code refactor
- Thats why you shouldn't dump commit messages to logs!
> since it's only relevant to devs
Since you are hosting your project on GitHub - you are expecting, that it not only for end-users, and for Developers also, huh? So, why not to maintain neat change log for them? (And use GitHub Releases for end-users change log, without "fine-grained details of every internal code refactor")
That said, I feel that changelogs are way better, being more flexible and more in control of the user. I do feel that a lot of people can't keep one that well though. We don't need fine-grained details of every internal code refactor on a major-release changelog, since it's only relevant to devs (and they'll usually see the commit logs anyway).
[1]: https://news.ycombinator.com/item?id=9237398