Re: Contribution checklist v2

[Joseph Myers <joseph at codesourcery dot com>]

On Mon, 7 Oct 2019, Siddhesh Poyarekar wrote:

> PS: I've dropped the ChangeLog section in that page and replaced it with
> a note pointing to the changelog generation script.

Note that the release checklist 
<https://sourceware.org/glibc/wiki/Release> needs updating to include the 
step of adding the generated ChangeLog in the release.  I think that comes 
right after updating version.h and features.h, and before tagging: run the 
script (in some way that needs to be documented) and commit the results as 
ChangeLog.  That thereby ensures the ChangeLog is in release tarballs 
without needing to change how those tarballs are created.

I think ChangeLog should be renamed now (at the point where we stop 
writing ChangeLog entries manually) to ChangeLog.old/ChangeLog.19.

Then, another step in the release process, after branching, along with 
updating version.h and NEWS, should be renaming that generated ChangeLog 
for the previous release to the next ChangeLog.old/ChangeLog.<number>.  So 
the normal state on master would be that there is no file called 
ChangeLog, just ChangeLog.old/*, but that release tarballs do include 
ChangeLog with the changes from the most recent release (and changes from 
previous releases in ChangeLog.old/*).

-- 
Joseph S. Myers
joseph@codesourcery.com