cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Pötz <>
Subject Re: [Vote] new "importance" attribute on in status.xml
Date Tue, 09 Mar 2004 14:37:11 GMT
Sylvain Wallez wrote:

> Carsten Ziegeler wrote:
>> It seems that we need a place where we can put "important changes" 
>> for 2.1.5.
>> This is currently the renaming of woody to cocoon forms and the 
>> incompatible excalibur-logger change that might cause problems with 
>> existing installations.
>> Apart from putting it on the Wiki has someone a good idea where to 
>> place such things so that they are visible for people downloading or 
>> extracting the distribution? Perhaps a "Readme.1st" etc.
> Once again the need arises to categorize changes ;-)
> Let's finally introduce this "importance" attribute on <action> 
> elements, that will allow to clearly distinguish changes. It can be 
> used to organize the release notes page (important changes come first) 
> and also to filter the announcement email (only important changes are 
> relevant here).
> I also propose that each block has its own status.xml file. The main 
> status.xml will be used for changes to the core, and also change of 
> block status (creation, deprecation, etc).
> So let's finally vote on this.
> - do you want to add an importance="high|low|medium" attribute on 
> <action> in changes.xml?

I think high|low|medium should me more meaningful or in other words 
self-explaining. What about "newFeature", "incompatibleChange", 

> - do you want each block to have it's own status.xml file?

As long as we dont have RCB (real Cocoon blocks) I'm in favour of Vadims 


View raw message