From dev-return-23507-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Thu Oct 07 17:22:14 2010
Return-Path: <dev-return-23507-apmail-apr-dev-archive=apr.apache.org@apr.apache.org>
Delivered-To: apmail-apr-dev-archive@www.apache.org
Received: (qmail 17072 invoked from network); 7 Oct 2010 17:22:13 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 7 Oct 2010 17:22:13 -0000
Received: (qmail 39741 invoked by uid 500); 7 Oct 2010 17:22:13 -0000
Delivered-To: apmail-apr-dev-archive@apr.apache.org
Received: (qmail 39664 invoked by uid 500); 7 Oct 2010 17:22:12 -0000
Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:dev@apr.apache.org>
List-Help: <mailto:dev-help@apr.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@apr.apache.org>
List-Id: <dev.apr.apache.org>
Delivered-To: mailing list dev@apr.apache.org
Delivered-To: moderator for dev@apr.apache.org
Received: (qmail 79902 invoked by uid 99); 7 Oct 2010 16:39:39 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of wmrowe@gmail.com designates 209.85.160.50 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from
         :user-agent:mime-version:to:subject:references:in-reply-to
         :content-type:content-transfer-encoding;
        bh=6P0/99g453UP4JgW9h1inYdCyl0GovpM99tl3oBj4VM=;
        b=K+tHbUDvKiLl7bl2T7UxapxRiKYJnhaG3tQOwfYZr/OI61Xeh2PKIIQWcFlpCM9wtG
         STOyeS84vnruIW4OEQ/FzbXbhCqEcf8VVV12nMbHZ1Ya3RjC0CdpdZX4OOIZoPnCnjzL
         FDT0kmXmGrEzC1Nbht2fjWCTrIACkqXu0wUyk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=OS+LRgIf3oMRM6jIb1YRPHdT9e5xyqf+Rc3gyVdkU+5+BAi8Dqtu0hgDOIH1gtzxrt
         x6U7OHmQxmtJV2RgWUvfKA9vG6GskBbUiS1L5TllGRG37HtVjjMvE/BTgjnkSt276OOZ
         gQwptqfbXKcn7aNsqCt96YnsrHAPzcybiMph4=
Message-ID: <4CADF7A3.6020001@gmail.com>
Date: Thu, 07 Oct 2010 11:38:59 -0500
From: "William A. Rowe Jr." <wmrowe@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: dev@apr.apache.org
Subject: Re: [Vote] apr-util 1.5.x -> trunk
References: <20101005074049.GA10384@redhat.com> <4CACCD67.50606@rowe-clan.net> <AANLkTindtEjD62tft4oEwBpLZ7BYO_FY=tyR=zPVHgNJ@mail.gmail.com> <77B9677A-03A0-4E9F-8A94-06A863B1CFB6@sharp.fm>
In-Reply-To: <77B9677A-03A0-4E9F-8A94-06A863B1CFB6@sharp.fm>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 10/7/2010 5:29 AM, Graham Leggett wrote:
> 
> We will still need to make releases on apr-util in the v1.x series, and we may need to
> bump v1.3 to v1.4, etc. For this, we need a properly functional trunk, otherwise those
> following the standard svn conventions face problems.

Yes, and no.  1.x APR is similarly retired.  It doesn't live on a trunk/ either.

1.x APR-util cannot build against APR trunk/, so I fail to see how this logic
holds.  If APR 1.4 becomes APR 1.5 becomes APR 1.6, this fork occurs from the
APR 1.x-1 branch, not from APR 2.