Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 87406 invoked from network); 1 Apr 2004 10:35:09 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 1 Apr 2004 10:35:09 -0000 Received: (qmail 26313 invoked by uid 500); 1 Apr 2004 10:34:38 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 26246 invoked by uid 500); 1 Apr 2004 10:34:38 -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 26219 invoked from network); 1 Apr 2004 10:34:36 -0000 Received: from unknown (HELO mail.s-und-n.de) (212.8.217.2) by daedalus.apache.org with SMTP; 1 Apr 2004 10:34:36 -0000 Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id 2500A19F5C8 for ; Thu, 1 Apr 2004 12:34:50 +0200 (CEST) Received: from hw0386 ([10.10.2.54]) by notes.sundn.de (Lotus Domino Release 6.5) with ESMTP id 2004040112282979-18038 ; Thu, 1 Apr 2004 12:28:29 +0200 From: "Carsten Ziegeler" To: Subject: RE: [VOTE RESULT] javaflow Date: Thu, 1 Apr 2004 12:37:05 +0200 Organization: S&N AG MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <406BEBFB.3040903@vafer.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcQX0YFplSoOoPgJTl+nkwM0VA7jOAAA4Hrg X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 01.04.2004 12:28:29, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 01.04.2004 12:28:30, Serialize complete at 01.04.2004 12:28:30 Message-ID: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" 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 Torsten Curdt wrote: > > > > Rule No.1 in OS projects: NEVER TRUST THE RELEASE MANAGER! > > hehe ...you wanna shirk the responsibility ;) but I trust you > anyway :) > Hey, it was worth a try :) Thanks! > >>that he will not forget > >>to change it when it is on his todo list for the release ;-) But I > >>have absolutely no problem with disabling in dev by default. > >> > >>...I known about it and have my local blocks properties > file anyway ;) > >> > > > > Actually it's not that big deal, we should either disable it now, > > but then I'd propose to disable *all* unstable blocks > Oh no, please not because this will lead to everyone wanting to declare his favorite block "stable" :) > > or add the instruction to disable the block to the wiki > (the release > > process description), so the release manager can't forget it :) > > as you like :) > Let's just disable the java flow block in the CVS - we all use our own properties file anyway. Carsten