On Tue, 2018-02-13 at 12:07 -0800, Adam Williamson wrote: > On Mon, 2018-02-12 at 11:59 -0500, David Cantrell wrote: > > The dist-git changelogs are mostly noise and I would prefer better > > organized information about impacts to users and developers. Like > > tell > > me what things changed in the new glibc package, not that the glibc > > RPM > > has been upgraded to the new release. I can figure out that part > > myself. > > As an alternative perspective on this, I am *constantly* frustrated > by > the lack of detail in SCM commit messages, and would much prefer far > more of it. I frequently find myself wanting to know exactly why > someone did something seven years ago, and find it entirely > impossible > to answer the question from the information available. Yes! As a lifelong developer and user with the gray hair of "been there, done that" I couldn't agree more with this sentiment. SCM messages are for developers, not users. I want an SCM message to briefly summary WHAT happened and then in detail WHY it happened. The changed code itself gives details of WHAT and if it's unclear it ought have comments in the code, not the SCM message. Users, on the other hand, likely don't care about any of that, unless they too are a developer. Fine, they don't need anything else. Plain, non-developer users however, need to know HOW this impacts them and might appreciate the WHY. Beyond that, I really don't care how we get there. But IMHO, that should be the goal. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
