Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 93676 invoked from network); 20 Nov 2004 14:47:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Nov 2004 14:47:22 -0000 Received: (qmail 38516 invoked by uid 500); 20 Nov 2004 14:47:21 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 38475 invoked by uid 500); 20 Nov 2004 14:47:20 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 38455 invoked by uid 99); 20 Nov 2004 14:47:20 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [212.23.3.141] (HELO heisenberg.zen.co.uk) (212.23.3.141) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 20 Nov 2004 06:47:17 -0800 Received: from [82.69.78.226] (helo=[192.168.0.2]) by heisenberg.zen.co.uk with esmtp (Exim 4.30) id 1CVWW7-0005Jw-JC; Sat, 20 Nov 2004 14:47:11 +0000 Message-ID: <419F58EE.2020407@apache.org> Date: Sat, 20 Nov 2004 14:47:10 +0000 From: Ross Gardler User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lenya Developers List CC: Forrest Developers List Subject: Re: generating the changes.xml from svn References: <419EA6C7.1030407@apache.org> <419EE488.9070803@apache.org> In-Reply-To: <419EE488.9070803@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-Heisenberg-IP: [82.69.78.226] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N [cross posted to Forrest-dev] Gregor J. Rothfuss wrote: > Gregor J. Rothfuss wrote: > >> thanks to stefano, i learned about svn log -v --xml >> >> this results in a 3MB file that has all the commit logs since lenya >> cvs was started (january 2002). we can easily generate the forrest >> changes.xml out of it. i'll take a shot at the necessary xsl. >> >> for the future, this means we need to make an extra effort to have >> meaningful commit messages and atomic commits (to avoid duplicate >> messages about the same change). > > > ok, http://lenya.apache.org/changes.html This is cool and very good timing too because I just committed a logs plugin to Forrest. This plugin embeds log files (currently only J2SE Java logs) in a Forrest published site. The problem I see with generating changes.xml from svn logs is that the svn logs are too fine grained and often have multiple commits for the same/similar things (guidelines are all very well but it will still happen). There is certainly value in this level of detail for developers but for a changelog aimed at users when a release is made I think that there is an overwhelming amount of detail. So I have a suggestion: Status.xml remains as it is, manually maintained and used for user focussed changelogs (in the future we could have a token in the commit message indicate that the log entry is intended to be included in changes.html, but that is for later). Your stylesheet goes into the Forrest logs plugin and is used to generate a developer focussed changelog with links to the SVN diffs and all the cool stuff you have. Moving the stylesheet into a Forrest plugin will increase the number of projects using this and should result in many improvments such as those you suggest. I will move your stylesheet over to the Forrest plugin for you are OK with me doing that. Ross