On 30.01.21 11:39, John Paul Adrian Glaubitz wrote:
On 1/30/21 11:37 AM, Stefan Seyfried wrote:
On 29.01.21 15:32, John Paul Adrian Glaubitz wrote:
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?
But you usually only can read the changelog after installation of the package and then you have no idea if the version did change. Unless there is a changelog entry stating that.
No, I actually read changelogs in most cases when something suddenly breaks or behaves unexpectedly. Then looking at the changelog is the first place to find out what happened and why.
This is no contradiction to what I have written. How would you know that the version changed between two changelog entries? And is the "new upstream release x.y" not a good hint on what you might need to look additionally to debug why it behaves unexpectedly? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman