Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 24515 invoked from network); 11 Nov 2004 15:21:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 Nov 2004 15:21:11 -0000 Received: (qmail 67776 invoked by uid 500); 11 Nov 2004 15:21:09 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 67721 invoked by uid 500); 11 Nov 2004 15:21:09 -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 67702 invoked by uid 99); 11 Nov 2004 15:21:09 -0000 Received-SPF: pass (hermes.apache.org: local policy) Received: from [217.160.230.40] (HELO mout.perfora.net) (217.160.230.40) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 11 Nov 2004 07:21:09 -0800 Received: from minotaur.apache.org[209.237.227.194] (helo=[127.0.0.1]) by mrelay.perfora.net with ESMTP (Nemesis), id 0MKz5u-1CSGkx13c4-0006w2; Thu, 11 Nov 2004 10:21:03 -0500 X-Provags-ID: perfora.net abuse@perfora.net login:e2e4156964dfbcc4c642ec658fa7f9b9 Message-ID: <4193835C.4010305@reverycodes.com> Date: Thu, 11 Nov 2004 10:21:00 -0500 From: Vadim Gritsenko User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [Vote] Remove woody and portal-fw in 2.2? References: <939f0a1494fa73af1ab0028a.20041109135157.enycu.tbref@www.dslextreme.com> <33400.10.0.0.58.1100089233.squirrel@10.0.0.58> <41922752.20605@dslextreme.com> <41923C7B.5090106@reverycodes.com> <6db0af4ba55f5a82c8a.20041110080915.enycu.tbref@www.dslextreme.com> <4193393E.901@mobilebox.pl> <4193564C.1090009@upaya.co.uk> In-Reply-To: <4193564C.1090009@upaya.co.uk> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Upayavira wrote: > I thought we were working towards a single set of blocks shared between > both 2.1 and 2.2? If that is the case, we can't deprecate a block in 2.2 > and not in 2.1, at least not at the moment. We'd need a cleverer build > system, say one that knows which blocks to include from within the > blocks repository. We are not there yet, and some blocks differ between 2.1 and 2.2. Anyway, what's your vote? :) Vadim