This is the mail archive of the
mailing list for the glibc project.
Re: Hash out a solution for ChangeLog/NEWS at the Cauldron?
- From: Martin Sebor <msebor at gmail dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Siddhesh Poyarekar <siddhesh at redhat dot com>, libc-alpha at sourceware dot org, carlos at redhat dot com, roland at hack dot frob dot com
- Date: Tue, 04 Aug 2015 15:43:44 -0600
- Subject: Re: Hash out a solution for ChangeLog/NEWS at the Cauldron?
- Authentication-results: sourceware.org; auth=none
- References: <20150804173912 dot GC2504 at spoyarek dot pnq dot redhat dot com> <55C10308 dot 2050501 at gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1508042035190 dot 6522 at digraph dot polyomino dot org dot uk>
On 08/04/2015 02:37 PM, Joseph Myers wrote:
On Tue, 4 Aug 2015, Martin Sebor wrote:
What I'm thinking of is a policy that'll allow us to auto-generate
ChangeLog and NEWS from commit data so that whatever is posted on the
list can be git-am'd directly and merged into master without rewriting
the commit. This will allow for tighter integration with patchwork,
to mark committed patches as closed automatically, leaving just
superseded patches to clean up.
Would using Bugzilla to keep track of which release each bug was
fixed in be a appealing solution? It would make it easier to find
As long as it handles point releases (that is, can track that a bug was
fixed in 2.22.1 and 2.23, so the generated NEWS entries for both those
releases include that bug), it seems a reasonable approach.
The Target Milestone drop down box can only be used for a single
version. It's populated with minor release (and a few 2.2.x and
2.3.x ones). The Keywords free form text field has been used for
fixes backported to other releases so it should work for point
PS Here's a link to a search for all bugs whose Target Milestone
is set to 2.22. It currently returns 40 out of the 192 bugs listed
in the NEWS file in 2.22.