From dev-return-103875-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Sat Sep 8 18:13:11 2012 Return-Path: X-Original-To: apmail-cocoon-dev-archive@www.apache.org Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9E146DFF9 for ; Sat, 8 Sep 2012 18:13:11 +0000 (UTC) Received: (qmail 85604 invoked by uid 500); 8 Sep 2012 18:13:11 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 85386 invoked by uid 500); 8 Sep 2012 18:13:10 -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 85376 invoked by uid 99); 8 Sep 2012 18:13:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Sep 2012 18:13:10 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [88.149.128.104] (HELO smtpi4.ngi.it) (88.149.128.104) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Sep 2012 18:13:02 +0000 Received: from [192.168.1.2] (88-149-141-36.v4.ngi.it [88.149.141.36]) by smtpi4.ngi.it (Postfix) with ESMTP id CC802425C8 for ; Sat, 8 Sep 2012 20:12:40 +0200 (CEST) Message-ID: <504B8A98.8070501@apache.org> Date: Sat, 08 Sep 2012 20:12:40 +0200 From: =?ISO-8859-1?Q?Francesco_Chicchiricc=F2?= User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: release 2.2.1 References: <5049DD45.7070308@gmail.com> In-Reply-To: <5049DD45.7070308@gmail.com> Content-Type: multipart/alternative; boundary="------------070201000709000506070103" This is a multi-part message in MIME format. --------------070201000709000506070103 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit On 07/09/2012 13:40, Thorsten Scherler wrote: > Hi all, > > we from codebusters.es need a release 2.2.1 for one of our client. > > I applied some outstanding issue and for the 4 which are still open I > am not sure since I do not have any test case to test and some are > more wishes (like release). ;) Thorsten, this looks like a very nice news! > Is there any guideline I should follow to push out the release? I've only found [1], clearly outdated (Daisy stuff, for example); if you think it's useful anyway you might also be interested in updating [2]. > Naturally 2.1.x and 3 should as well be released ASAP, where I see the > 2.1 less complicated since it is a maintenance release. However we > lost a bit sight of doing an official c3 release and get a stable > version out there. IMO, for C3 we can still release a beta1-M1; I was actually waiting for COCOON3-100 to be fixed: I've reworked the proposed patch for fixing COCOON3-102 and can apply the same to COCOON3-100 as temporary solution. Regards. [1] http://cocoon.apache.org/1199_1_1.html [2] https://svn.apache.org/repos/asf/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ --------------070201000709000506070103 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 07/09/2012 13:40, Thorsten Scherler wrote:
Hi all,

we from codebusters.es need a release 2.2.1 for one of our client.

I applied some outstanding issue and for the 4 which are still open I am not sure since I do not have any test case to test and some are more wishes (like release). ;)

Thorsten,
this looks like a very nice news!

Is there any guideline I should follow to push out the release?

I've only found [1], clearly outdated (Daisy stuff, for example); if you think it's useful anyway you might also be interested in updating [2].

Naturally 2.1.x and 3 should as well be released ASAP, where I see the 2.1 less complicated since it is a maintenance release. However we lost a bit sight of doing an official c3 release and get a stable version out there.

IMO, for C3 we can still release a beta1-M1; I was actually waiting for COCOON3-100 to be fixed: I've reworked the proposed patch for fixing COCOON3-102 and can apply the same to COCOON3-100 as temporary solution.

Regards.

[1] http://cocoon.apache.org/1199_1_1.html
[2] https://svn.apache.org/repos/asf/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml
-- 
Francesco Chicchiriccò

ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/ 
--------------070201000709000506070103--