From: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
---|---|
To: | |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Deriving release notes from git commit messages |
Date: | 2011-06-24 18:47:46 |
Message-ID: | 4E04DBD2.6090706@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
From | Date | Subject | |
---|---|---|---|
Next Message | Jeroen Vermeulen | 2011-06-24 18:53:32 | Re: News on Clang |
Previous Message | Robert Haas | 2011-06-24 18:24:21 | Re: Optimizing pg_trgm makesign() (was Re: WIP: Fast GiST index build) |