Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-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 1CD1094E1 for ; Wed, 25 Apr 2012 11:53:15 +0000 (UTC) Received: (qmail 71399 invoked by uid 500); 25 Apr 2012 11:53:14 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 71340 invoked by uid 500); 25 Apr 2012 11:53:14 -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 71327 invoked by uid 99); 25 Apr 2012 11:53:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 11:53:14 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sberyozkin@gmail.com designates 209.85.214.41 as permitted sender) Received: from [209.85.214.41] (HELO mail-bk0-f41.google.com) (209.85.214.41) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 11:53:05 +0000 Received: by bkvi17 with SMTP id i17so1673355bkv.0 for ; Wed, 25 Apr 2012 04:52:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=xVrwNZ/a82QtcsR8oT6u79q3bQKs51yCu9skvkCBPgw=; b=xoly6UpOAJRuOJoRMkkUEGpnSAGZTMHGaqi3/VySZZ99ChWvdbtlV7ag1zbwXTFqrk ulrK9eYTDXgWA2byR5i1aVLxojSyaGnaBKdJIQMEpcF/0t+KHoNBd9kv2th84IyuPqfz JGgzglwljCFNw8N7QaVQzqSfJzUDdJUeO7UXq7CxorVxRI7mBLD3Zrjy7hbldp1HlGhy YANutshD6qlakX+9ZbPES1sglB0y3QSCK8VHO4PJZltWxaFFIVqBfquJPS4Wjva2bMca O42qFrax+mLzMmvLxPZZIpZ1XFwpmqVmVK0ffHIO1WpHdbREoGjAvgQzof+Z3mUnI4Cs cFmA== Received: by 10.204.152.75 with SMTP id f11mr528885bkw.136.1335354765370; Wed, 25 Apr 2012 04:52:45 -0700 (PDT) Received: from [192.168.2.3] ([89.100.141.106]) by mx.google.com with ESMTPS id g8sm13680784bkt.9.2012.04.25.04.52.44 (version=SSLv3 cipher=OTHER); Wed, 25 Apr 2012 04:52:44 -0700 (PDT) Message-ID: <4F97E58B.9070101@gmail.com> Date: Wed, 25 Apr 2012 12:52:43 +0100 From: Sergey Beryozkin User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11 MIME-Version: 1.0 To: dev@cxf.apache.org Subject: Re: [DISCUSS] Drop 2.3.x patches.... References: <3214981.D1Y6oeHOWI@dilbert.dankulp.com> In-Reply-To: <3214981.D1Y6oeHOWI@dilbert.dankulp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 24/04/12 19:30, Daniel Kulp wrote: > > Just wanted to open up a discussion about dropping support for 2.3.x. > 2.3.0 was release over 18 months ago. Since then, 2.4.x was released over a > year ago and 2.5.x 6 months ago. (and 2.6 last week). Thus, there has > been plenty of opportunity (a whole year) for people to upgrade to newer > versions. > > Right now, we have 4 branches we're supporting (2.6(trunk)/2.5/2.4/2.3) and > we're likely soon going to make a 2.6 branch and open up trunk for 2.7 work > adding yet another one. Dropping 2.3 will simplify things a bit for us. > > The major "con" to it is that there are still a lot of folks using 2.3.x. > According the Nexus stats of central, last month, 2.3.3 was still the second > most downloaded version. (next to 2.5.2) However, if they are on 2.3.3 > which was released over a year ago, they haven't been grabbing the latest > patches anyway so producing more patches won't really matter to them. > > In any case, I'm think about doing one more 2.3.x release (2.3.11) which > would be announced as the end of the 2.3.x line. Obviously if any > security issues pop up we can push another release in the future, but > basically end the regular patch releases. > Sounds good, 2.3.11 will be the best one in the 2.3.x line :-) > Any objections or other thoughts? > +1 Cheers, Sergey