> 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
>
Hi Ralph,
On 12/29/21 11:57 PM, Ralph Little wrote:
> Hi,
>
> On 2021-12-29 1:30 p.m., Povilas Kanapickas wrote:
>> Hello,
>>
>> There were some discussions on how to make handling release notes easier
>> in the past so that releases are not as difficult. Time has come to
>> actually implement
Hi Allan,
On 12/30/21 1:21 AM, m. allan noah wrote:
> I don't recall this conversation, where did it take place?
I've proposed this twice during the last year:
https://alioth-lists.debian.net/pipermail/sane-devel/2021-August/039081.html
and also in a our private email chain between Olaf and the
I don't recall this conversation, where did it take place?
In the past, we had a Changelog that everyone modified for every merge, and
it was largely a duplicate of their commit messages. So, we stopped doing
it. Are you proposing a return to that type of duplication?
allan
On Wed, Dec 29, 2021
Hi,
On 2021-12-29 1:30 p.m., Povilas Kanapickas wrote:
Hello,
There were some discussions on how to make handling release notes easier
in the past so that releases are not as difficult. Time has come to
actually implement them.
What changes?
Developers will need to write a short one or two
Hello,
There were some discussions on how to make handling release notes easier
in the past so that releases are not as difficult. Time has come to
actually implement them.
What changes?
Developers will need to write a short one or two sentence description to
a new file in newsfragments
