Re: Deriving release notes from git commit messages - Mailing list pgsql-hackers

From Greg Smith
Subject Re: Deriving release notes from git commit messages
Date
Msg-id 4E04DBD2.6090706@2ndQuadrant.com
Whole thread Raw
In response to Re: Deriving release notes from git commit messages  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Deriving release notes from git commit messages
Re: Deriving release notes from git commit messages
List pgsql-hackers
On 06/24/2011 01:42 PM, Robert Haas wrote:
> I am disinclined to add a "feature"
> annotation.  I think it is unlikely that will end up being any more
> useful than just extracting either the whole commit message or its
> first line.
>    

I don't see any good way to extract the list of commits relevant to the 
release notes without something like it.  Right now, you can't just mine 
every commit into the release notes without getting more noise than 
signal.  Something that tags the ones that are adding new features or 
other notable updates, as opposed to bug fixes, doc updates, etc., would 
allow that separation.

> I am not inclined to try to track sponsors in the commit message at
> all.

I was not suggesting that information be part of the commit.  We've 
worked out a reasonable initial process for the people working on 
sponsored features to record that information completely outside of the 
commit or release notes data.  It turns out though that process would be 
easier to drive if it were easier to derive a feature->{commit,author} 
list though--and that would spit out for free with the rest of this.  
Improving the ability to do sponsor tracking is more of a helpful 
side-effect of something that's useful for other reasons rather than a 
direct goal.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Optimizing pg_trgm makesign() (was Re: WIP: Fast GiST index build)
Next
From: Jeroen Vermeulen
Date:
Subject: Re: News on Clang