I guess I was thinking of something different for the NEWS/ChangeLog
than that - just something describing the high-level changes to the
project since the last release instead of a description of all the
commits.
If someone really wanted that level of detail, I think that git log
would be a much better route (easier to filter, colorized,
customizable
etc.).
I have exactly the same opinion. There is no sense in copying git log into a separate
file. Anyone wanting to see the list of commits can look into git directly, with much more
detail and possibilities than we can offer in a single file.
This file should contain only high-level list of changes. It can be just a few lines about
features added, bugs fixed, etc. No need to list every single typo-related commit that
happened. It can also speak in much more human language than commit messages usually do.
It is important to ask ourselves what we are trying to accomplish. I would like to give
people a short list of important changes in a release, similarly to what I do when
announcing new release in my blogposts. We can also include a recipe how to display the
full commit log.