From dev-return-103987-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Mon Nov 19 09:46:19 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 562A6DBC2 for ; Mon, 19 Nov 2012 09:46:19 +0000 (UTC) Received: (qmail 14786 invoked by uid 500); 19 Nov 2012 09:46:18 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 14611 invoked by uid 500); 19 Nov 2012 09:46:17 -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 14573 invoked by uid 99); 19 Nov 2012 09:46:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Nov 2012 09:46:16 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [93.93.44.98] (HELO lanfeust.anyware.corp) (93.93.44.98) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Nov 2012 09:46:09 +0000 Received: from localhost (localhost [127.0.0.1]) by lanfeust.anyware.corp (Postfix) with ESMTP id 18D0D9F6D for ; Mon, 19 Nov 2012 10:45:39 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at lanfeust.anyware.corp Received: from lanfeust.anyware.corp ([127.0.0.1]) by localhost (lanfeust.anyware [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wqTb5hP7hyVy for ; Mon, 19 Nov 2012 10:45:38 +0100 (CET) Received: from [172.31.2.33] (maya.anyware.corp [172.31.2.33]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lanfeust.anyware.corp (Postfix) with ESMTPSA id 8C59F1B9 for ; Mon, 19 Nov 2012 10:45:38 +0100 (CET) Message-ID: <50A9FFD2.7090808@anyware-services.com> Date: Mon, 19 Nov 2012 10:45:54 +0100 From: =?ISO-8859-15?Q?C=E9dric_Damioli?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [DISCUSS] Releasing 2.1.12 References: <50A91C4C.6010100@apache.org> In-Reply-To: <50A91C4C.6010100@apache.org> X-ZohoCRM-Archived: none Content-Type: multipart/alternative; boundary="------------000406040905040601030105" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------000406040905040601030105 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Hi, Le 18/11/2012 18:35, Francesco Chicchiriccò a écrit : > Hi all (but Cédric in particular), > by looking at JIRA [1] it seems that quite a considerable number of > issues have been fixed since 2.1.11 (31) even though some are still > standing (11+2). > > Following our recent discussion in another thread, I have some > questions to Cédric (and other C2.1 devs, if there are...): > > 1. Do you think that the the 13 outstanding issues can be moved to > 2.1.13 or there are some that need to be absolutely included in 2.1.12? 3 of them were opened by myself before gaining committership. [1] [2] [3] I could have closed them already, but was waiting for others' approval. I don't know if someone has something to say about them ... The 10 others issues are more than 2 years old There are also 74 issues with no "fix for" version (29 with a patch included) but affecting a 2.1.x version We should maybe ask 2.1 users if there are particular issues they want to be fixed before cutting a 2.1.12 ? > > 2. Is the release process clear to you? If not, who (maybe active in > the past) can provide some hint? Not really. I think there was once a page written by Carsten describing the release process, but I can't find it anymore. > > 3. Do you need any help in the release process? If so, who is > available to help? I am, even though I don't remember pretty anything > of C2.1... Yes please It would be great if 2 or 3 people other than me could try to run unit tests and run samples. Almost 5 years after the 2.1.11, I also don't remember all blocks, it would be great to also have feedbacks from users of some specific blocks. > > 4. Considering the questions above, when do you think we can start > releasing 2.1.12? Depending if we try to gather some feedbacks from devs and users or not, it could be quite fast, say in the next few days. But 5 years after, we can afford one or two more weeks if needed > > Thanks for info. > Regards. > > [1] > https://issues.apache.org/jira/browse/COCOON/fixforversion/12312903#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel > [1] https://issues.apache.org/jira/browse/COCOON-2288 [2] https://issues.apache.org/jira/browse/COCOON-2313 [3] https://issues.apache.org/jira/browse/COCOON-2314 Best regards, -- Cédric Damioli Ametys CMS http://www.ametys.org http://www.anyware-services.com --------------000406040905040601030105 Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit
Hi,

Le 18/11/2012 18:35, Francesco Chicchiriccò a écrit :
Hi all (but Cédric in particular),
by looking at JIRA [1] it seems that quite a considerable number of issues have been fixed since 2.1.11 (31) even though some are still standing (11+2).

Following our recent discussion in another thread, I have some questions to Cédric (and other C2.1 devs, if there are...):

 1. Do you think that the the 13 outstanding issues can be moved to 2.1.13 or there are some that need to be absolutely included in 2.1.12?
3 of them were opened by myself before gaining committership. [1] [2] [3]
I could have closed them already, but was waiting for others' approval. I don't know if someone has something to say about them ...

The 10 others issues are more than 2 years old

There are also 74 issues with no "fix for" version (29 with a patch included) but affecting a 2.1.x version

We should maybe ask 2.1 users if there are particular issues they want to be fixed before cutting a 2.1.12 ?


 2. Is the release process clear to you? If not, who (maybe active in the past) can provide some hint?
Not really.
I think there was once a page written by Carsten describing the release process, but I can't find it anymore.


 3. Do you need any help in the release process? If so, who is available to help? I am, even though I don't remember pretty anything of C2.1...
Yes please
It would be great if 2 or 3 people other than me could try to run unit tests and run samples.
Almost 5 years after the 2.1.11, I also don't remember all blocks, it would be great to also have feedbacks from users of some specific blocks.


 4. Considering the questions above, when do you think we can start releasing 2.1.12?
Depending if we try to gather some feedbacks from devs and users or not, it could be quite fast, say in the next few days.
But 5 years after, we can afford one or two more weeks if needed



Thanks for info.
Regards.

[1] https://issues.apache.org/jira/browse/COCOON/fixforversion/12312903#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel

[1] https://issues.apache.org/jira/browse/COCOON-2288
[2] https://issues.apache.org/jira/browse/COCOON-2313
[3] https://issues.apache.org/jira/browse/COCOON-2314

Best regards,

--------------000406040905040601030105--