Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <5027EA83.6000805@rowe-clan.net>
Date: Sun, 12 Aug 2012 10:40:19 -0700
From: "William A. Rowe Jr." <wrowe@rowe-clan.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: dev@apr.apache.org
Subject: Re: [VOTE] Release apr-util 1.5.0
References: <201208062224.52416.sf@sfritsch.de> <5024E2A3.6070705@kippdata.de>
 <201208102205.00717.sf@sfritsch.de>
In-Reply-To: <201208102205.00717.sf@sfritsch.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 8/10/2012 1:05 PM, Stefan Fritsch wrote:
> Thanks for the detailed tests.
> 
> On Friday 10 August 2012, Rainer Jung wrote:
>> If you don't need to release before, I would like to fix the LDADD
>> use over the weekend, but it is not a show stopper.
> 
> It seems I will be busy in the next few days. It is unlikely that I 
> T&R 1.5.1 before next Wednesday.
> 
>> Another nice to have would be an expat update to 2.1.0.
> 
> Has anyone looked into this before and knows how much work this is?

I have an alternate suggestion as of 1.5 - to drop our embedded expat
just as we did in trunk.  Require the user to obtain the (now once
again maintained) expat package.

> Another nice to have fix would be support for newer Berkley DB 
> versions (PR 53684).

And I'd also like to incorporate the rfc implementation of punycode
encode/decode for use by any i18n domain features of our consumers,
such as httpd or even client apps.  Would anyone mind, if I can get
this into the tree by tuesday aftn?  As 1.5.0 wasn't released, I don't
think the binary compatibility is an issue just yet.