Re: Contribution Checklist - ChangeLog

[Carlos O'Donell <carlos@redhat.com>]

On 8/20/20 1:58 PM, Siddhesh Poyarekar wrote:
> On 20/08/20 14:12, Siddhesh Poyarekar wrote:
>> My personal bias is towards not having to write ChangeLog entries at
>> all.  We could make it happen by backporting the ChangeLog script to
>> older stable branches and then drop the ChangeLog requirement altogether.
>>
>> As an aside, I'm thinking of separating out the stable branch (and all
>> of the old addons, ports, etc.) related stuff out into a separate page
>> so that this checklist remains short and simple.  Stable branches have
>> historically only been touched by distribution maintainers and I doubt
>> if that will change in the near future given that we don't cut releases
>> off stable branches.  I'll do this too tonight if nobody objects.
> 
> Aha, so this is where I updated the Checklist and then forgot to merge
> the changes in:
> 
> https://sourceware.org/glibc/wiki/Contribution%20checklist%20v2
> 
> I'll hack on this to get y'all to review and this time around, remember
> to merge the changes back :)

I would *love* v2 of the checklist to become *live* ... are you going to:

(a) Edit v1 with the ChangeLog changes. 

or

(b) Edit v2 and propose we use that.

My opinion is that backports to stable branches should *not* update the
ChangeLog.

The ChangeLog is only valid at the time a tarball is created.

If a stable branch has a release then the VCS update scripts will be used
to update the ChangeLog.

-- 
Cheers,
Carlos.