Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 28983 invoked from network); 20 Nov 2007 23:32:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Nov 2007 23:32:25 -0000 Received: (qmail 36469 invoked by uid 500); 20 Nov 2007 23:32:10 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 36389 invoked by uid 500); 20 Nov 2007 23:32:10 -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 36378 invoked by uid 99); 20 Nov 2007 23:32:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Nov 2007 15:32:10 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.86.168.178] (HELO mxout-03.mxes.net) (216.86.168.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Nov 2007 23:31:58 +0000 Received: from [192.168.0.125] (unknown [212.76.37.214]) by smtp.mxes.net (Postfix) with ESMTP id 3037523E4AC for ; Tue, 20 Nov 2007 18:31:49 -0500 (EST) Message-ID: <47436E64.1010407@apache.org> Date: Wed, 21 Nov 2007 00:31:48 +0100 From: Grzegorz Kossakowski User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: lenya 2.0 release preparation - cocoon version dependency (2.1.11?) References: <473C5AB5.1070402@apache.org> <473C6537.60407@apache.org> <473EAB2C.2030902@dslextreme.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Bertrand Delacretaz pisze: > On Nov 17, 2007 9:49 AM, Ralph Goers wrote: >> ...If someone finds a bug and wants to fix it and do a release of 2.1.x >> they should be free to do so.... > >> Grzegorz Kossakowski wrote: > > Agree with Ralph, there's no need to "close" anything, if people want > to fix bugs on older versions that's one of the beauties of open > source: no one forces you to upgrade, as long as you're ready to fix > what you're using if needed. Ok, lesson taken. :-) Just to clarify, we don't have policy to keep 2.1 and trunk in sync, anymore. Right? -- Grzegorz Kossakowski Committer and PMC Member of Apache Cocoon http://reflectingonthevicissitudes.wordpress.com/