Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 99909 invoked from network); 31 Dec 2007 13:32:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Dec 2007 13:32:31 -0000 Received: (qmail 38624 invoked by uid 500); 31 Dec 2007 13:32:19 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 38537 invoked by uid 500); 31 Dec 2007 13:32:18 -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 38526 invoked by uid 99); 31 Dec 2007 13:32:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Dec 2007 05:32:18 -0800 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of grek@tuffmail.com designates 216.86.168.178 as permitted sender) Received: from [216.86.168.178] (HELO mxout-03.mxes.net) (216.86.168.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Dec 2007 13:32:07 +0000 Received: from [192.168.0.195] (unknown [89.174.126.134]) by smtp.mxes.net (Postfix) with ESMTP id DA5EE23E4A8 for ; Mon, 31 Dec 2007 08:31:57 -0500 (EST) Message-ID: <4778EFB6.4090704@tuffmail.com> Date: Mon, 31 Dec 2007 14:33:42 +0100 From: Grzegorz Kossakowski User-Agent: Thunderbird 2.0.0.9 (X11/20070801) MIME-Version: 1.0 To: Cocoon's dev mailing list Subject: Outstanding issues need to be fixed before 2.2 final release Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello, As we all expecting 2.2 final to be released very soon I decided to revisit all issues with '2.2' set as fix-for version. I pushed most of them to next releases because they are not blockers. I left only those that I consider to be serious enough that they deserve our attention before making final release of 2.2 or it seemed that only only trivial action is needed to be performed in order to close them. The list is here: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310170&fixfor=12310611&resolution=-1&sorter/field=priority&sorter/order=DESC (COCOON-2065 can be ignored, it is on the list because patch was not applied on 2.1.x branch) If you think this list lacks any critical issue please add it ASAP. If no action will be taken on them within two upcoming weeks I think we should release 2.2 final in a state as it is now. WDYT? -- Grzegorz Kossakowski