Re: [COMMITTERS] pgsql: Also update ChangerLog file.
From:
Magnus Hagander <magnus(at)hagander(dot)net>
To:
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc:
Michael Meskes <meskes(at)postgresql(dot)org>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject:
Re: [COMMITTERS] pgsql: Also update ChangerLog file.
On Sat, Jan 9, 2010 at 17:55, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michael Meskes <meskes(at)postgresql(dot)org> writes:
>> On Fri, Jan 08, 2010 at 03:41:10PM +0100, Stefan Kaltenbrunner wrote:
>>> Hmm not sure I find that commit message really helpful - but is it
>>> actually of any use to maintain a Changelog file specifically for
>>> ECPG?
>
>> Makes it easier to see what's new in ecpg when doing a new
>> release. But I guess we could get all this from the cvs log too. The
>> file has been there for a long time.
>
> Well, I'm pretty sure that release notes are prepared off of the cvs log
> entries. I've never looked at ecpg's Changelog when working on notes,
> and I'd be prepared to bet that Bruce hasn't either. My advice is to
> drop the Changelog file and be sure you describe changes appropriately
> in the commit messages.
+1.
Seems really weird (and unnecessary) to have a changelog for just one
small "subsystem", when we don't have it for the others.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
