Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 11265 invoked from network); 30 Mar 2007 15:32:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Mar 2007 15:32:32 -0000 Received: (qmail 82128 invoked by uid 500); 30 Mar 2007 15:32:36 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 82054 invoked by uid 500); 30 Mar 2007 15:32:36 -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 List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 82043 invoked by uid 99); 30 Mar 2007 15:32:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Mar 2007 08:32:35 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [86.59.12.200] (HELO mx-02.sil.at) (86.59.12.200) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Mar 2007 08:32:27 -0700 Received: from [86.59.20.138] (helo=[10.4.1.249]) by mx-02.sil.at with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.60) (envelope-from ) id 1HXJ5B-0006K1-Ef for dev@cocoon.apache.org; Fri, 30 Mar 2007 17:32:05 +0200 Message-ID: <460D2D72.2020604@apache.org> Date: Fri, 30 Mar 2007 17:32:02 +0200 From: Reinhard Poetz User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Make status code attribute of seriailzers expandable References: <460CFDEF.3000000@apache.org> <460D2265.3060708@apache.org> <460D27E6.2090300@apache.org> <460D2B9C.1060908@apache.org> In-Reply-To: <460D2B9C.1060908@apache.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Scan-Signature: f774a900875950925d5dec44e3e19685 X-Virus-Checked: Checked by ClamAV on apache.org Grzegorz Kossakowski wrote: > As for RC1... Yes, it means that we will stop massive changes and polish > things (like DOCUMENTATION) after RC1 is released. I guess final/next > candidate release would follow RC1 really soon. However, Reinhard seems > to have better idea of current plan. Unless we have big concerns, we should have only one series of release candidates and than a final release of all modules that have been releases as milestones so far. As said some days ago, I plan to release in the week after the Easter break. Releasing more than half of ours modules is *a lot* of work. After the series of final releases (scheduled for May), we should only release modules that have significant improvements or bugfixes. -- Reinhard P�tz Independent Consultant, Trainer & (IT)-Coach {Software Engineering, Open Source, Web Applications, Apache Cocoon} web(log): http://www.poetz.cc --------------------------------------------------------------------