Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 82957 invoked from network); 9 Aug 2006 06:05:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Aug 2006 06:05:02 -0000 Received: (qmail 18679 invoked by uid 500); 9 Aug 2006 06:05:00 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 18614 invoked by uid 500); 9 Aug 2006 06:04:59 -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 18603 invoked by uid 99); 9 Aug 2006 06:04:59 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO [127.0.0.1]) (209.237.227.194) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Aug 2006 23:04:59 -0700 Message-ID: <44D97B55.4070308@apache.org> Date: Wed, 09 Aug 2006 08:06:13 +0200 From: Carsten Ziegeler User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [Vote] Java 5 as minimum JDK requirement References: <44D88E48.7000601@apache.org> <44D89A3E.4040708@lojjic.net> <1155074397.18488.31.camel@jjohnston> <44D96E9B.1070206@dslextreme.com> In-Reply-To: <44D96E9B.1070206@dslextreme.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Ralph Goers wrote: > The folks who are decided to maintain their blocks this way did it with > the clear understanding that this was the price they would have to pay, > so I don't think the clarification is necessary. I can recall at least > one instance where a change to one of these blocks had to be backed or > modified because it broke the 2.1.x branch. Remember, we voted a while > ago for trunk to only support 1.4 and up while 2.1.x supports 1.3, so > this problem already exists. > Yepp, and I think as soon as we have 2.2 out, we should not share these blocks with 2.1.x anymore as all new features should go to 2.2 only. 2.1.x is then a real maintenance branch where we only do minor improvements and bugfixing. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/