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: Siddhesh Poyarekar <siddhesh at redhat dot com>, libc-alpha at sourceware dot org
- Cc: carlos at redhat dot com, roland at hack dot frob dot com, joseph at codesourcery dot com
- Date: Tue, 04 Aug 2015 12:23:04 -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>
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
them and generate useful reports for each release. Such reports
are often helpful when deciding which release to adopt. The NEWS
file could also be generated from such a report just before each