Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 85330 invoked from network); 9 Sep 2003 09:16:13 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 9 Sep 2003 09:16:13 -0000 Received: (qmail 2585 invoked by uid 500); 9 Sep 2003 09:15:43 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 2534 invoked by uid 500); 9 Sep 2003 09:15:43 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 2516 invoked from network); 9 Sep 2003 09:15:42 -0000 Received: from unknown (HELO grunt24.ihug.com.au) (203.109.249.144) by daedalus.apache.org with SMTP; 9 Sep 2003 09:15:42 -0000 Received: from p886-apx1.syd.ihug.com.au (expresso.localdomain) [203.173.143.124] by grunt24.ihug.com.au with esmtp (Exim 3.35 #1 (Debian)) id 19webA-000755-00; Tue, 09 Sep 2003 19:15:44 +1000 Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian)) id 19wech-0000kJ-00 for ; Tue, 09 Sep 2003 19:17:19 +1000 Date: Tue, 9 Sep 2003 19:17:19 +1000 From: Jeff Turner To: forrest-dev@xml.apache.org Subject: Re: Mixed-namespace support (Re: cvs commit: ...) Message-ID: <20030909091719.GA2416@expresso.localdomain> Mail-Followup-To: forrest-dev@xml.apache.org References: <20030908134815.85048.qmail@minotaur.apache.org> <20030908232710.GB65879@minotaur.apache.org> <3F5D24BA.3090308@che-che.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F5D24BA.3090308@che-che.com> User-Agent: Mutt/1.5.4i 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 On Tue, Sep 09, 2003 at 02:54:18AM +0200, Juan Jose Pablos wrote: > Jeff, > > I personally thought that we were going to let a bit more time to test > forrest with cocoon 2.1.1 (2 weeks). Why bother? We'll get a lot more testers by releasing 0.5 now and releasing 0.5.1 if we discover any bugs in Cocoon. > But for some reason you want to release this ASAP, that is ok, but given > that people hurried to commit stuff, can we delay this release for > Wednesday? Looks like it. --Jeff > >Does all this stuff (and @class) *have* to happen a few hours before 0.5 > >gets released? Couldn't it wait 24 hours for 0.6, when we have a decent > >multi-namespace validation system[1] in place? > > > >Same for @class attributes -- I don't care whether it's good or bad; I > >don't want to even consider it for 0.5. We can do a 0.5.1 any time. > > > > > >--Jeff > > > cheers, > cheche > > BTW: 0.4 and 0.2RC1 were released on Wednesday. >