From dev-return-97395-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Tue Nov 06 20:39:10 2007 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 78346 invoked from network); 6 Nov 2007 20:39:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Nov 2007 20:39:10 -0000 Received: (qmail 50223 invoked by uid 500); 6 Nov 2007 20:38:56 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 50155 invoked by uid 500); 6 Nov 2007 20:38:56 -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 50144 invoked by uid 99); 6 Nov 2007 20:38:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Nov 2007 12:38:56 -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, 06 Nov 2007 20:38:57 +0000 Received: from [192.168.0.127] (unknown [212.76.37.154]) by smtp.mxes.net (Postfix) with ESMTP id 3762F23E49F for ; Tue, 6 Nov 2007 15:38:36 -0500 (EST) Message-ID: <4730D0CA.2040507@apache.org> Date: Tue, 06 Nov 2007 21:38:34 +0100 From: Grzegorz Kossakowski User-Agent: Thunderbird 2.0.0.5 (X11/20070719) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Preparing Cocoon 2.2-final References: <47132601.2060606@apache.org> <4714C9B0.3020900@reverycodes.com> <4715B2B0.9040708@uninett.no> In-Reply-To: <4715B2B0.9040708@uninett.no> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hanne Moa pisze: > > How about a samples block, or marking what will and won't work in the > samples for 2.1.10 on 2.2? Yes, that is quite important. I think it would be very nice if someone could iterate over all samples of all released (or planned for a release) blocks and report what's not working. Then we could decide if we are going to fix them or mark as not working at the time. -- Grzegorz Kossakowski Committer and PMC Member of Apache Cocoon http://reflectingonthevicissitudes.wordpress.com/