Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 57733 invoked from network); 27 Oct 2009 16:02:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Oct 2009 16:02:48 -0000 Received: (qmail 22497 invoked by uid 500); 27 Oct 2009 16:02:47 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 22436 invoked by uid 500); 27 Oct 2009 16:02:47 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 22426 invoked by uid 99); 27 Oct 2009 16:02:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2009 16:02:47 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of asoldano@redhat.com designates 209.132.183.28 as permitted sender) Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2009 16:02:39 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n9RG2InD025944 for ; Tue, 27 Oct 2009 12:02:18 -0400 Received: from [10.3.226.39] (vpn-226-39.phx2.redhat.com [10.3.226.39]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n9RG2HYi015099 for ; Tue, 27 Oct 2009 12:02:17 -0400 Message-ID: <4AE71988.4020202@redhat.com> Date: Tue, 27 Oct 2009 17:02:16 +0100 From: Alessio Soldano User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: dev@cxf.apache.org Subject: Re: Ideas for 2.2.5 and end of year References: <200910231544.11030.dkulp@apache.org> In-Reply-To: <200910231544.11030.dkulp@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12 X-Virus-Checked: Checked by ClamAV on apache.org I'm fine with a 2.2.5 happening soon. Cheers Alessio Daniel Kulp wrote: > Just wanted to start a discussion about 2.2.5. I know it's a bit early since > 2.2.4 was just released 2 weeks ago, but holiday season is fast approaching so > I thought I throw an idea out there. > > We've done a TON of work resolving JIRA issues in the last two weeks. We > already have over 30 resolved issues on the 2.2.x branch which is outstanding > work. That's already more than we had for 2.1.7. Thus, I was kind of > thinking of doing a 2.2.5 sooner than the normal 8-10 weeks. > > 8-10 weeks from the last release would put it at about mid December, which > kind of sucks due to holidays and such. I know I'm going to be in and out > throughout December (I have too many "use or lose" vacation days) and I know > others will be in and out as well. Thus, it's not really a good time to > prepare a release. Thus, I was thinking maybe do 2.2.5 in mid November and > then 2.2.6 would then be in January sometime. (and then I'm hoping 2.3 would > be in Feb/Mar, but that still remains to be seen if stuff is "ready") > > I don't think there is much push for 2.1.8 for November. Only 9 of the > resolved issues were pushable back to 2.1.x. Thus, I'd probably skip 2.1.8 > and just do that in January with 2.2.6. Besides, I'd like to slow down 2.1.x > releases with the thought of stopping them sometime soon as well since 2.2.x > is generally a simple migration from 2.1.x. > > Does that make sense to people? Any objections? Thoughts? Comments? > > -- Alessio Soldano Web Service Lead, JBoss