Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of trawick@gmail.com designates
 209.85.215.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=celLjFL4dgK5IpGYyCGf90Wfsf8PZyD0e5sCYxe+0f65wHboeJe/LrK3GySREz1Z4N
         eBMEXFN4CwPAco+vh63DeXvaHRsjqAGBqhMOO8Yq15Ww7+4HoXeiPNkPh9KzFCFq62e5
         /Z5jSB7iG7NwcJsF/ddmGv98kN5zUFlg0C3B0=
MIME-Version: 1.0
In-Reply-To: <77B9677A-03A0-4E9F-8A94-06A863B1CFB6@sharp.fm>
References: <20101005074049.GA10384@redhat.com>
	<4CACCD67.50606@rowe-clan.net>
	<AANLkTindtEjD62tft4oEwBpLZ7BYO_FY=tyR=zPVHgNJ@mail.gmail.com>
	<77B9677A-03A0-4E9F-8A94-06A863B1CFB6@sharp.fm>
Date: Thu, 7 Oct 2010 07:26:52 -0400
Message-ID: <AANLkTindD3joW4NoUYPqqAM9Nvyz=uGMWoHeiJC94bpa@mail.gmail.com>
Subject: Re: [Vote] apr-util 1.5.x -> trunk
From: Jeff Trawick <trawick@gmail.com>
To: dev@apr.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 7, 2010 at 6:29 AM, Graham Leggett <minfrin@sharp.fm> wrote:
> On 07 Oct 2010, at 12:22 PM, Jeff Trawick wrote:
>
>> These choices seem skewed to me. =A0"apr is apr-util/trunk" is a
>> different concept than "rename 1.5.x to trunk." =A0Conceptually, "apr is
>> apr-util trunk" whatever we decide.
>
> I disagree, in the past, we had two projects, each with an independent tr=
unk
> and release cycle, one called apr, the other called apr-util. We have cho=
sen
> to retire the apr-util project, and have copied the functionality into ap=
r,
> but that doesn't make the apr-util project go away.

Maybe we're disagreeing to agree ;)  All I (we) mean by "apr is
apr-util" trunk from a conceptual standpoint is that we expect new
features to the "util" part of the code will go to apr trunk first,
then potentially be backported to the apr-1.x-compatible "util"
codebase (which happens to be in a separate tree).

> We will still need to make releases on apr-util in the v1.x series, and w=
e
> may need to bump v1.3 to v1.4, etc. For this, we need a properly function=
al
> trunk, otherwise those following the standard svn conventions face proble=
ms.

yep