From: Brian Lyles <brianmlyles@gmail.com>
Date: Fri, 22 Mar 2024 01:22:22 GMT
Subject: Re: What's cooking in git.git (Mar 2024, #05; Tue, 19)
Message-ID: <17bef197ac874ae6.70b1dd9aae081c6e.203dcd72f6563036@zivdesk>
In-Reply-To: <xmqq34sjd9h0.fsf@gitster.g>

Hi Junio

On Thu, Mar 21, 2024 at 8:02 AM Junio C Hamano <gitster@pobox.com> wrote:

> "Brian Lyles" <brianmlyles@gmail.com> writes:
> 
>> A strategy that I have seen work well is for any commit making a notable
>> change (one that should appear in the release notes) to include an entry
>> in a CHANGELOG.NEXT.md file.
> 
> While I very much like the idea of distributing the burden of coming
> up with an initial draft for an entry in the final release notes, I
> am not convinced that the approach to use a single in-tree file
> would work well in our distributed development style where the
> history is merge-heavy with many topics in flight in parallel.
> 
> I can imagine how well the approach for each contributor to give
> such a draft entry in the cover letter of their topic would work;
> it would be with much less friction compared to a single in-tree
> file that will be the source of merge conflicts.

Yes, I suspect you are right. I think the cover letter would be a good
start at the very least. Would you welcome a patch to
'Documentation/SubmittingPatches' that adds a new expectation for this,
or do you think this would be best handled yourself? I am interested in
contributing but, as I'm sure you've noticed, I'm also quite new to the
project =)

-- 
Thank you,
Brian Lyles