Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 64395 invoked from network); 10 May 2006 09:09:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 May 2006 09:09:57 -0000 Received: (qmail 40957 invoked by uid 500); 10 May 2006 09:09:55 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 40454 invoked by uid 500); 10 May 2006 09:09:53 -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 40443 invoked by uid 99); 10 May 2006 09:09:53 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED 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; Wed, 10 May 2006 02:09:53 -0700 Message-ID: <4461AE0F.6010407@apache.org> Date: Wed, 10 May 2006 11:10:39 +0200 From: Carsten Ziegeler User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: ApacheCon Hackaton: focus on 2.2? References: <4460A595.6000700@apache.org> <4460AB74.2050608@apache.org> <4460C76F.9030407@thebug.it> <4460D193.3080707@apache.org> In-Reply-To: <4460D193.3080707@apache.org> 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 Reinhard Poetz wrote: > I don't understand what this thread is about. We can discuss it for ages what we > *want* to do but this doesn't necessarily mean that something will really > happen. If there is enough involvement to get 2.2 (didn't we decide to call it > "2.3"?) out of the door it will happen, if not, nothing will happen. The same is > true for 3.0 (= with OSGi). Personally I don't have a problem if both release > cycles start around the same point of time. > Hmm, I thought this thread is about focusing involvement to get a release out. So what is wrong about discussing a(nother) possible release plan? Some of us see the need to discuss these things, so please let them do this. If we wouldn't need further information, we could just release today - and I guess this is nothing anyone of us wants, right? Ok, getting more constructive - I think our biggest problem *today* is the incomplete build system - we need a system which builds a running Cocoon version *including* the blocks and the samples. Imho, we should have this before the hackaton. I know we have already talked about this "for ages" and nothing happened. So are there any volunteers who have some spare time to finish the work? (As a motivation for this: if this person is comming to Dublin, I guess everyone of the Cocoon community will buy him/her a beer - or whatever drink is prefered) Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/