List of fixed bugs in NEWS now automatically generated

[Joseph Myers <joseph at codesourcery dot com>]

The list of fixed bugs in the NEWS file will now be automatically 
generated at release time using scripts/list-fixed-bugs.py.  You should no 
longer insert bug numbers in NEWS when committing bug fixes to master.  
Instead, when you commit a patch that completely fixes a bug, you need to 
set the milestone (to the next mainline release, so 2.23 at present) when 
resolving the bug as FIXED.

There is no change to ChangeLog handling; [BZ #N] should continue to be 
used there on any patch relevant to a bug, including partial fixes as well 
as complete fixes.  Also, on release branches the list of fixed bugs in 
NEWS still needs updating manually (since there are no point releases at 
present, an automatically-generated list would never get added on a 
release branch).  For 2.23 and later release branches you should use the 
same format for the manually-maintained list as for the 
automatically-generated list; for existing release branches, use the 
existing format.

If posting a patch that is only a partial fix for a bug, it's helpful to 
say explicitly in the patch posting and commit message that it's only a 
partial fix, to avoid people thinking that you may have forgotten to close 
the bug as FIXED.

I've updated what I think are the relevant wiki pages:

https://sourceware.org/glibc/wiki/Bugzilla%20Procedures
https://sourceware.org/glibc/wiki/Committer%20checklist
https://sourceware.org/glibc/wiki/Release

If making further changes to bug list generation (e.g. if moving / 
renaming the script), consider whether further updates to those pages are 
needed.

-- 
Joseph S. Myers
joseph@codesourcery.com