Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 34418 invoked from network); 12 Nov 2009 10:01:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Nov 2009 10:01:29 -0000 Received: (qmail 99323 invoked by uid 500); 12 Nov 2009 10:01:29 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 99233 invoked by uid 500); 12 Nov 2009 10:01:28 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 99225 invoked by uid 99); 12 Nov 2009 10:01:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 10:01:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of paul@querna.org designates 209.85.210.171 as permitted sender) Received: from [209.85.210.171] (HELO mail-yx0-f171.google.com) (209.85.210.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 10:01:20 +0000 Received: by yxe1 with SMTP id 1so1848141yxe.3 for ; Thu, 12 Nov 2009 02:00:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.90.16.40 with SMTP id 40mr4277181agp.7.1258020059657; Thu, 12 Nov 2009 02:00:59 -0800 (PST) In-Reply-To: <4AFB4B0D.2080800@rowe-clan.net> References: <4AFB4B0D.2080800@rowe-clan.net> Date: Thu, 12 Nov 2009 02:00:59 -0800 Message-ID: <4239a4320911120200t1291cdc2xe945bbd76877ee5f@mail.gmail.com> Subject: Re: Future tag plans From: Paul Querna To: "William A. Rowe Jr." Cc: APR Developer List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Nov 11, 2009 at 3:38 PM, William A. Rowe Jr. wrote: > If nobody objects, I'll plan to tag 1.4.0 this coming Monday 11/16 > (it so happens to be after all my deadlines and right before more > work obligations, so there a hole right there to fill). =C2=A0Should give > anyone sufficient time to wrap up their inspection of the API and > code changes. I object. The crypto API still has issues, which as far as I can remember from the last thread, have not been completely addressed: Considering APR's versioning policy, I don't really feel comfotable setting that API in stone, unless people more familiar with the issue speak up loudly saying its perfect. > If nobody objects, I'll plan to tag 2.0.0 on 12/21 (during the start > of my holidays) - which adds 4+ weeks beyond the close of a 1.4.0 > vote during which time folks are free to fix broken API declarations, > drop deprecated interfaces, rename wonky function names and generally > just make-ready for a GA. I don't see a point in APR 2.x at this point, I am personally having doubts about APRs perspecitve on lots of decisions, and kinda wish we went the ultra-light-weight Moccasin approach, with at a minimum, optional pools. I don't think APR 2.x is progressing fast enough right now to say we should set a date to release it. Thanks, Paul