[sane-devel] Upcoming changes for handling release notes

[Wolfram Sang]

> I don't think we should duplicate commit messages. Release notes are for
> end users, commit messages are for other developers, so good release
> note and good commit message are completely different. It makes sense to
> write a release note only if the change impacts end users in a
> noticeable way. Many commits are refactorings and similar changes, so
> they don't need a release note.

Good you made that clear. I was also wondering why we don't simply
utilize the commit message. But the above makes sense to me, so I agree
to the proposal. Thanks for doing it!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20211231/c1c49dd2/attachment.sig>