Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <419CE6DB.103@apache.org>
Date: Thu, 18 Nov 2004 10:15:55 -0800
From: Stefano Mazzocchi <stefano@apache.org>
Organization: Apache Software Foundation
User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103)
MIME-Version: 1.0
To: dev@cocoon.apache.org
CC: karim.lakhani@sloan.mit.edu
Subject: Re: [MIT Research Project] Identifying "features" in Cocoon 2.1
References: <419B7781.7030105@mit.edu>
In-Reply-To: <419B7781.7030105@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Karim R. Lakhani wrote:

> Please nominate features and I will summarize what was reported back to 
> the community.  I will then do the "dirty work" of compiling and 
> matching it to the CVS commits and the email discussion:)  Of course all 
> my findings and writings will be public as well.

Karim,

I was thinking that one possible way to do this, could be that you 
compile a list, based on the cross-correlation between the CVS logs (too 
granular) and the changes.xml file (eventually still too granular) and 
then we filter it out here.

The reason for this is that, honestly, I don't remember *when* something 
was added :-) so indicating a period of time is rather hard for us to 
correlate with specific features (several blocks were added, for 
example, but don't remember which ones).

CVS/SVN logs contain all that information, it's just a matter of 
filtering it out. A way to do this would be to remove all the logs that 
resulted in a few lines of code of change.

Ah, note that if you use "svn log -v --xml" you get an xml format of the 
logs and you can use cocoon to filter that out ;-)

Seriously, I think asking for a list of features correlated with time 
yields a "bah, can't remember" answer, while a list of things to look at 
might allow us to say "oh yeah, that one".

WDYT?

-- 
Stefano.