Date: Mon, 22 Dec 2008 09:28:11 -0300
From: Alvaro Herrera <alvherre@commandprompt.com>
To: w^3 <pgsql-www@postgresql.org>
Subject: publishing changelogs on pgweb
Message-ID: <20081222122811.GA10220@alvh.no-ip.org>
References: <200707111306.l6BD69G14356@momjian.us>
	<25050.1184164913@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <25050.1184164913@sss.pgh.pa.us>
User-Agent: Mutt/1.5.18 (2008-05-17)

Hi,

This was proposed over a year ago, here
http://archives.postgresql.org/message-id/25050.1184164913%40sss.pgh.pa.us

Any thoughts on how could we do it?  Maybe a hook on the anoncvs
auto-update thing, that regenerated a set of static files?


Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Alvaro Herrera wrote:
> >> Hmm, do we include the cvs2cl-generated ChangeLog in the tarballs?
> 
> > No, we don't.  We used to but the file got too large.  Perhaps we should
> > supply a URL that generates that information.
> 
> There are a couple of different queries that people would be interested
> in:
> 
> * the full cvs2cl log between any two release points;
> * the cvs2cl log from latest release to branch tip.
> 
> I do not think it's appropriate to stick this into the tarballs, as
> there's an awful lot of noise in the logs (eg, docs tweaks, reverted
> patches, trivial code cleanups); our practice of generating a condensed
> release-notes page is a large public service in my eyes.  But +1 to
> providing a web page from which the detailed answers could be generated
> easily.
> 
> BTW, cvs2cl (at least the version I use) works fine against a remote
> repository, so it's not like Ray couldn't have gotten the answer for
> himself.  But a web page would be more user-friendly.
> 
> 			regards, tom lane


-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support