X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 3D7299FB4EE for ; Sat, 2 Sep 2006 14:27:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 31225-03 for ; Sat, 2 Sep 2006 14:27:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by postgresql.org (Postfix) with ESMTP id 682649FB4AB for ; Sat, 2 Sep 2006 14:27:00 -0300 (ADT) Received: from mailgate.vale-housing.co.uk ([194.217.48.34] helo=vale-housing.co.uk) by anchor-post-34.mail.demon.net with esmtp (Exim 4.42) id 1GJZGl-0000qB-E5 for pgsql-hackers@postgresql.org; Sat, 02 Sep 2006 17:26:59 +0000 Received: from 89.240.228.119 ([89.240.228.119]) by ratbert.vale-housing.co.uk ([192.168.1.106]) with Microsoft Exchange Server HTTP-DAV ; Sat, 2 Sep 2006 17:26:59 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Sat, 02 Sep 2006 18:31:51 +0100 Subject: Re: Postgres tracking - the pgtrack project From: Dave Page To: Tom Lane , Greg Sabino Mullane CC: Message-ID: Thread-Topic: [HACKERS] Postgres tracking - the pgtrack project Thread-Index: AcbOpnuY/JAh4ZXNQO2HHNeSXXEVVgADzEzH In-Reply-To: <3454.1157211745@sss.pgh.pa.us> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/167 X-Sequence-Number: 89696 On 2/9/06 16:42, "Tom Lane" wrote: > BTW, another "output" thing you might consider is "having draft release > notes ready-to-go on demand". Currently, Bruce prepares the release > notes on the basis of a very tedious scan of the CVS commit logs. > If this sort of stuff were being dropped into a tracker as it went > into the CVS tree, at least the research part of making the notes would > be zero-effort (or perhaps better to say that the work would be spread > out instead of concentrated). We have the developers update the CHANGELOG file with each non-trivial change in pgAdmin. It works very well for us and producing release announcements etc. is a trivial task. The overhead on each developer is virtually zero as well as they have to compose some text for the commit message anyway. http://www.pgadmin.org/development/changelog.php Regards, Dave.