cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <reinh...@apache.org>
Subject Re: change file maintenance, Re: svn commit: r518990 - in /cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src: changes/changes.xml main/java/org/apache/cocoon/generation/ExceptionGenerator.java
Date Fri, 16 Mar 2007 15:15:00 GMT
Vadim Gritsenko wrote:
> vgritsenko@apache.org wrote:
>>  <document>
>>    <body>
>> -    <release version="1.0.0-M1-SNAPSHOT" date="2007-00-00" 
>> description="unreleased">
>> +    <release version="1.0.0-RC1-SNAPSHOT" date="TBA" 
>> description="Unreleased">
>> +    </release>
>> +    <release version="1.0.0-M1" date="2007-02-12" 
>> description="Milestone release">
> 
> Shouldn't / can't this be done by the release process?

that would be great but I don't think that there is support for this

> I'd go one step further and suggest that current tag on this module is 
> bad since tagged changes had incorrect version and release date, which 
> would lead to incorrect website pages generated for the module.
> 
> At the very least, this has to be done before tagging. Right now I had 
> to hunt for release date using 'svn log', and I'm sure I easily could 
> make a mistake here.

agreed but I don't know of anything better than using the changes plugin :-(

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Mime
View raw message