Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 46376 invoked from network); 9 Mar 2004 13:29:30 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 9 Mar 2004 13:29:30 -0000 Received: (qmail 67477 invoked by uid 500); 9 Mar 2004 13:29:24 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 67422 invoked by uid 500); 9 Mar 2004 13:29:24 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 67408 invoked from network); 9 Mar 2004 13:29:23 -0000 Received: from unknown (HELO trinity.anyware-tech.com) (217.112.237.100) by daedalus.apache.org with SMTP; 9 Mar 2004 13:29:23 -0000 Received: (qmail 4224 invoked from network); 9 Mar 2004 13:29:23 -0000 Received: from unknown (HELO apache.org) (10.1.0.254) by trinity.anyware-tech.com with SMTP; 9 Mar 2004 13:29:23 -0000 Message-ID: <404DC6B2.8060809@apache.org> Date: Tue, 09 Mar 2004 14:29:22 +0100 From: Sylvain Wallez Organization: Anyware Technologies User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [Vote] new "importance" attribute on in status.xml References: <404DC31A.3020409@apache.org> <404DC447.2000608@reverycodes.com> In-Reply-To: <404DC447.2000608@reverycodes.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 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 >> 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 will initially decide for the importance, and this can be later discussed if other don't agree, although I don't think this will happen often. >> - 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 ;-) > Let's do instead: > > * Do you want to add a block="name" attribute on in > changes.xml? > > +1 Good. The important point is to have a per-block classification, even if I personally prefer a per-block file. Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }