[Vote] new importance attribute on in status.xml (was: Re: Doc about important changes)

2004-03-09 Thread Sylvain Wallez
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

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Sylvain Wallez
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

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Vadim Gritsenko
Sylvain Wallez wrote: So let's finally vote on this. - do you want to add an importance=high|low|medium attribute on action in changes.xml? +0.5. How importance is defined - what is important and what is not? - do you want each block to have it's own status.xml file? -0, reduces

Re: [Vote] new importance attribute on in status.xml (was: Re: Doc about important changes)

2004-03-09 Thread Bertrand Delacretaz
Le Mardi, 9 mars 2004, à 14:14 Europe/Zurich, Sylvain Wallez a écrit : - do you want to add an importance=high|low|medium attribute on action in changes.xml? +1 - do you want each block to have it's own status.xml file? +0.5 (trying to be more precise in votes: I'm for it but cannot help ATM)

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Sylvain Wallez
Vadim Gritsenko wrote: Sylvain Wallez wrote: So let's finally vote on this. - do you want to add an importance=high|low|medium attribute on action in changes.xml? +0.5. How importance is defined - what is important and what is not? Really subjective, I admit. The one that makes the change

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Geoff Howard
Vadim Gritsenko wrote: Sylvain Wallez wrote: So let's finally vote on this. - do you want to add an importance=high|low|medium attribute on action in changes.xml? +.5 - do you want each block to have it's own status.xml file? -0, reduces visibility. Let's do instead: * Do you want to

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Vadim Gritsenko
Sylvain Wallez wrote: Vadim Gritsenko wrote: Sylvain Wallez wrote: ... - do you want each block to have it's own status.xml file? -0, reduces visibility. Having a separate file doesn't mean it doesn't appear on a different page in the docs. Cocoon has some nice features for aggregation ;-)

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Juan Jose Pablos
Sylvain, I remember looking on this issue on the forrest list a while ago. What about impact instead of importance? Cheers, Cheche Sylvain Wallez wrote: So let's finally vote on this. - do you want to add an importance=high|low|medium attribute on action in changes.xml? - do you want each

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Sylvain Wallez
Juan Jose Pablos wrote: Sylvain, I remember looking on this issue on the forrest list a while ago. What about impact instead of importance? Mmmh... impact has the underlying meaning that it will have some negative effects on some existing applications, which is not the case for 99% of

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Daniel Fagerstrom
Sylvain Wallez wrote: snip/ So let's finally vote on this. - do you want to add an importance=high|low|medium attribute on action in changes.xml? +1 - do you want each block to have it's own status.xml file? +1 /Daniel

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Tim Larson
On Tue, Mar 09, 2004 at 03:37:11PM +0100, Reinhard P?tz wrote: Sylvain Wallez wrote: Carsten Ziegeler wrote: 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

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Sylvain Wallez
Reinhard Pötz wrote: Sylvain Wallez wrote: snip/ - 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, minorChange? These

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Juan Jose Pablos
Reinhard Pötz wrote: I think high|low|medium should me more meaningful or in other words self-explaining. What about newFeature, incompatibleChange, minorChange? Well if the output of that is going to be just more visibility to some actions, then this will increase complexity adding poor

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Joerg Heinicke
On 09.03.2004 15:27, Juan Jose Pablos wrote: Mmmh... impact has the underlying meaning that it will have some negative effects on some existing applications, which is not the case for 99% of changes (we are careful about back compatibility). I was looking for a name, and I found weight as well

Re: [Vote] new importance attribute on in status.xml

2004-03-09 Thread Joerg Heinicke
On 09.03.2004 14:14, Sylvain Wallez wrote: - do you want to add an importance=high|low|medium attribute on action in changes.xml? +1 @importance or @impact - do you want each block to have it's own status.xml file? +0 Vadim wrote: * Do you want to add a block=name attribute on action in