This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: List of fixed bugs in NEWS now automatically generated
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Thu, 5 Nov 2015 23:18:26 +0000
- Subject: Re: List of fixed bugs in NEWS now automatically generated
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1511052229290 dot 8571 at digraph dot polyomino dot org dot uk> <20151105230432 dot 305A22C3B4C at topped-with-meat dot com>
On Thu, 5 Nov 2015, Roland McGrath wrote:
> > https://sourceware.org/glibc/wiki/Bugzilla%20Procedures
>
> This page still talks about "ports", so it might be out of date in other ways.
It probably is. I just dealt with the stuff about milestones that I think
was *never* accurate (it described procedures that were never used).
> Did we decide how we're handling backports to release branches in the new
> scheme?
The list of bugs fixed after the initial release still needs updating
manually, because we don't currently do point releases so there would
never be a point at which the release manager runs the script for the
branch. (And, thus, we don't need an extra Bugzilla field to store
information about branches to which a fix was backported, which we would
need if generating that list automatically.)
For existing release branches, the list stays in the old format. For 2.23
and later branches, the list of backported fixes should be in the new
format (via people cut-and-pasting the bug summary).
--
Joseph S. Myers
joseph@codesourcery.com