Re: [Clirr-devel] CVS: clirr/src/java/net/sf/clirr/checks MethodSetCheck.java,1.6,1.7

[<lak...@t-...>]

Sending on behalf of Vincent

 > -----Original Message-----
 > From: cli...@li... [mailto:clirr-devel-
 > ad...@li...] On Behalf Of Lars Kühne
 > Sent: 09 June 2004 07:28
 > To: cli...@li...
 > Subject: Re: [Clirr-devel] CVS: clirr/src/java/net/sf/clirr/checks
 > MethodSetCheck.java,1.6,1.7
 >
 > Simon Kitching wrote:
 >
 > >On Wed, 2004-06-09 at 04:30, Lars Kühne wrote:
 > >
 > >
 > >>Simon,
 > >>
 > >>could you please add the new feature to xdocs/changes.xml, so everyone
 > >>knows the differences between each release?
 > >>
 > >>
 > >
 > >Yes I can do.
 > >
 > >
 > >
 >
 > Thanks.
 >
 > >But ..umm.. doesn't clirr generate a nice report that tells us that?
 > >
 > >This was the initial reason I wanted a clirr-like tool; I was preparing
 > >release notes for Digester 1.6, and wanted to know what APIs had
 > >changed.
 > >
 > >
 > >
 >
 > Thats correct, Clirr tells you the API differences. When you are working
 > on a project that has the goal of producing an API (like
 > commons-collections) that might be sufficient. But for applications
 > (like Clirr), users are interested in a much more high level report.
 >
 > I think it's the same with JIRA and the Changelog it produces: Nice for
 > developers, but not suitable for end users.
 >
 > Everytime I create a release of our commercial software, I have to
 > create an end-user change log manually. Our customers don't want to know
 > that we have introduced ValueTypes, and optimized our caching algorithm
 > (that would be the Jira issues). In the releasenotes I would write
 > "performance has been improved dramatically", collapsing several jira
 > issues into one high level entry in our release notes.
 >
 > My goal with changes.xml is to tell clirr users what has changed from
 > their perspective - given they don't know the implementation, they just
 > want to use the tool.

Exactly! That was exactly my goal when I created the Maven changes 
plugin :-)

Glad someone has understood this! In maven land several person keep 
adding "developer" changes to changes.xml that are not interesting for 
end users (like "refactoring of such and such thing").

-Vincent