OK, so to choose some examples:
- the removal of gvbuffstderr.c should not get a changelog entry because no users or people building from source would notice
- the unsuppressing of ps2pdf errors should get a changelog entry because it changes build dependencies
Does this sound like the correct intuition? I deliberately picked two changes that are pretty close together in terms of what type of “user” is likely to see the impact.
To channel some of @ellson’s comments, I think we have three categories of “user”:
- end user downloading e.g. an rpm
- end user building from source
- developer hacking in the Graphviz tree
Changes deserve a changelog entry if they impact (1) or (2) or both. Changes can be omitted from the changelog if they only impact (3), who can get their knowledge from the commit log. Do I have that right?