Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 3018 invoked from network); 23 Mar 2011 21:34:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Mar 2011 21:34:30 -0000 Received: (qmail 16741 invoked by uid 500); 23 Mar 2011 21:34:29 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 16679 invoked by uid 500); 23 Mar 2011 21:34:29 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 16672 invoked by uid 99); 23 Mar 2011 21:34:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Mar 2011 21:34:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mdiggory@gmail.com designates 209.85.216.172 as permitted sender) Received: from [209.85.216.172] (HELO mail-qy0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Mar 2011 21:34:21 +0000 Received: by qyk29 with SMTP id 29so4517461qyk.3 for ; Wed, 23 Mar 2011 14:34:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=s3fFCQByaParaVP38Y22AElbiJWKHtNOGGth7kDjZrM=; b=P2cLqhIF2B/wDGrhGn8XBnANDNvVFiu8F0+klmEqrpWahHs480K8HTi+QMiF/nTEhz xAHUrWka6Fk/dyVroZMaTYRZMDsx+POTuU6hE6a+Z9YLeF1ZoBvZYEIuf1GeRxgdZbxs RLDbSozqKp98ZcfQiFfK/MgfxPAfve/PFmx0I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=PgXDVArHjwBTIk3cKuF4huufy1oZ4cQSTwsOnSNXgDjHXS3lDjvrJNeZuXCcd4c2Sk K6fuv9nYlZ8X5GU9Z2AjfONWV1K3sdMhcYR/k7SPLhdXPqvt3xdjs1s8KD7ApkeKTSML W3jt9EIgFtRArrFrPGuiwKQW0ikHlhbI8sGRA= MIME-Version: 1.0 Received: by 10.229.124.145 with SMTP id u17mr6417345qcr.71.1300916040667; Wed, 23 Mar 2011 14:34:00 -0700 (PDT) Received: by 10.229.245.10 with HTTP; Wed, 23 Mar 2011 14:34:00 -0700 (PDT) Date: Wed, 23 Mar 2011 14:34:00 -0700 Message-ID: Subject: Any planned release of Cocoon 2.2.1 or 2.3? Or should we just be trying to use 3.0-beta? From: Mark Diggory To: users@cocoon.apache.org Content-Type: multipart/alternative; boundary=000e0cd25cae7c9412049f2d1e23 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd25cae7c9412049f2d1e23 Content-Type: text/plain; charset=UTF-8 Seems like a considerable amount of time has gone by without a formal cocoon release, we are relying on patched/hacked releases of our one fixes to cocoon 2.2 modules because the most recent releases of these modules do not seem to play well together for us. See: https://issues.apache.org/jira/browse/COCOON-2265 We int he DSpace community would really like to see a release of Cocoon 2.2.x off the dev trunk or a full release of 3.0 since our project has become so invested in it. Is there any planned timeframe for this happening in your community? Best Regards, Mark Diggory --000e0cd25cae7c9412049f2d1e23 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Seems like a considerable amount of time has gone by without a formal cocoo= n release, we are relying on patched/hacked releases of our one fixes to co= coon 2.2 modules because the most recent releases of these modules do not s= eem to play well together for us. =C2=A0See:


We int he DSpace community would really like to see a release of Coco= on 2.2.x off the dev trunk or a full release of 3.0 since our project has b= ecome so invested in it. =C2=A0Is there any planned timeframe for this happ= ening in your community?

Best Regards,
Mark Diggory
--000e0cd25cae7c9412049f2d1e23--