This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Hash out a solution for ChangeLog/NEWS at the Cauldron?

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.

> 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
> release.

A script to generate the list of fixed bugs for NEWS, which then gets 
manually inserted in the checked-in file just before release, would also 
seem reasonable, given the mix of different types of content in NEWS.

Joseph S. Myers

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]