Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 8D9BC64FC32 for ; Mon, 22 Dec 2008 08:43:22 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 05541-07 for ; Mon, 22 Dec 2008 08:43:20 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by mail.postgresql.org (Postfix) with ESMTP id D79CE64FC23 for ; Mon, 22 Dec 2008 08:43:19 -0400 (AST) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 952E8DCC2DF; Mon, 22 Dec 2008 13:43:17 +0100 (CET) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mha-laptop.hagander.net (Postfix) with ESMTP id 0C6F41240C5; Mon, 22 Dec 2008 13:43:17 +0100 (CET) Message-ID: <494F8B64.2020504@hagander.net> Date: Mon, 22 Dec 2008 13:43:16 +0100 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: Alvaro Herrera CC: w^3 Subject: Re: publishing changelogs on pgweb References: <200707111306.l6BD69G14356@momjian.us> <25050.1184164913@sss.pgh.pa.us> <20081222122811.GA10220@alvh.no-ip.org> In-Reply-To: <20081222122811.GA10220@alvh.no-ip.org> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/143 X-Sequence-Number: 16320 Seems doable, at least in theory :) I've actually been toying with this a bit earlier, trying to get a summary of the CVS log messages into a database. That could be used to genereate pretty much anything. I ended up using the git repository instead, because it was easier - but given that it appears to be fairly fragile, I don't think that'd be a good idea in a case like this. IIRC, cvs2cl can actually produce XML output, which we could "easily" process and stick in a database, and then from there to the web. Adding this intermediate step would allow us to produce the output in multiple formats - for example, it wouldn't surprise me if people would appreciate an RSS feed... (Again, I've used the git repo for this myself, but that's proven to not be so good) Not sure how to solve the second of Toms points there automatically though - IIRC I hadn't solved the issue of getting the tags in there. I think it's easier to just run it with a cronjob, rather than trying to put more stuff into the commit hooks. We could still use it to trigger a run if the runs appear to be too slow - but I don't think we need anything like 5-minute granularity on the updates (which is the main reason for that commit hook) //Magnus Alvaro Herrera wrote: > 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 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 > >