On 1/29/21 3:22 PM, Neal Gompa wrote:
And why not? He's the changelog author.
Because changelog have a function. They're not written for the sake of creativity.
At least he's not being stupid and lazy like a lot of other people and straight up importing Git commit logs into changelogs.
There is nothing wrong with that as long as some formatting and filtering is applied. It would be easier if some upstream projects, especially Go and web projects are guilty of that, wouldn't abuse the git log as their personal diary. I have seen lots of Go projects with commit messages like "Hmm, that previous one didn't work, try again". Or something like "fix", "fix again", "sigh" and whatnot. That completely defeats the point of a commit message which is to document what got changed.
I generally despise almost *all* of openSUSE's policies around package changelogs, because they're wasteful, stupid, and encourage people to *not* read them because they're too dense. I deal with it because I *have* to, not because I *want* to.
If you don't want to add anything to a changelog, what would be the purpose of a changelog anyway. What's the point of an entry like "New upstream release" when there is zero other information added? I mean, the fact that there is a new upstream release is something that is obvious from the version of the package being changed, isn't it? Adrian