Return-Path: X-Original-To: apmail-httpd-dev-archive@www.apache.org Delivered-To: apmail-httpd-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 41972CAB6 for ; Tue, 2 Jul 2013 14:26:46 +0000 (UTC) Received: (qmail 72598 invoked by uid 500); 2 Jul 2013 14:23:37 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 71427 invoked by uid 500); 2 Jul 2013 14:23:12 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 71172 invoked by uid 99); 2 Jul 2013 14:21:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 14:21:33 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of michaelm12-asfbugzilla@aquaorange.net designates 82.68.126.114 as permitted sender) Received: from [82.68.126.114] (HELO kingpin.mjmm.org) (82.68.126.114) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 14:21:28 +0000 X-UVLTD-MailScanner-From: michaelm12-asfbugzilla@aquaorange.net X-UVLTD-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.399, required 5.1, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, HTML_MESSAGE 0.00, KHOP_THREADED -1.50) X-UVLTD-MailScanner: Found to be clean X-UVLTD-MailScanner-ID: r62EKkk2021296 X-UVLTD-MailScanner-Information: UnitVector Ltd processed this message Received: from [192.168.1.83] (dhcp83.mjmm.org [192.168.1.83]) (authenticated bits=0) by kingpin.mjmm.org (8.14.4/8.14.4/Debian-2ubuntu2) with ESMTP id r62EKkk2021296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 2 Jul 2013 15:20:49 +0100 Message-ID: <51D2E1BD.6050101@aquaorange.net> Date: Tue, 02 Jul 2013 15:20:45 +0100 From: MikeM User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: [discussion] Release 2.0.65 [the final frontier] References: <20130701164719.ec908e91c20de17e6e448089a4bc3ed2.6bf7abf572.wbe@email11.secureserver.net> <51D2C235.1030000@apache.org> <51D2CD35.707@aquaorange.net> In-Reply-To: Content-Type: multipart/alternative; boundary="------------060901090809000005010607" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.3.9 (kingpin.mjmm.org [192.168.1.12]); Tue, 02 Jul 2013 15:20:49 +0100 (BST) X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No This is a multi-part message in MIME format. --------------060901090809000005010607 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi Oh I see - I had not realised this. In that case, I agree that sticking with 0.9.x is the only sensible option at this point in time :) Mike On 02/07/2013 14:35, Jeff Trawick wrote: > On Tue, Jul 2, 2013 at 8:53 AM, MikeM > > wrote: > > Hi, > > Maybe the simple option is to do the final release with the > old/existing bundled APR, but put a foot note in the release notes > that the newer APR v1.4.8/1.5.2 has been confirmed to successfully > work with 2.0.65. This way it may give confidence to anyone who is > stuck on 2.0.x for some reason to use the newer APR/APR-util if > needs be. > > > APR/APR-util 1.x won't work with httpd 2.0.x. Someone continuing to > use 2.0.x will need to hand-pick or backport fixes from apr/apr-util > 0.9.x or later levels. But then they'll have to backport fixes from > httpd too. The line was drawn at slightly different places for httpd > vs. apr/apr-util, but the long term picture is the same: There is > effort to remain on httpd 2.0.x if you want to pick up any code fixes, > and the recommendation is clear. > > > > Regards, > Mike > > > On 02/07/2013 13:06, Guenter Knauf wrote: > > Hi Bill, > On 02.07.2013 01:47, wrowe@rowe-clan.net > wrote: > > I am not at all concerned > whether APR 0.9 is > released again or not since folks had years to take that > up in our > discussions of > putting httpd 2.0 to bed, yet nobody so much as suggested > a release, > nevermind some > volunteer to act on it. > > true; but I thought that most of us probably forgot about that > we bundle APR/APU with 2.0.x - like I did; the lack of APR/APU > fixes came only to my attention when I was on building the > 2.0.65 binaries ... > but since nobody else expressed an oppinion about then thats > fine, and I shut up. > > or if you have concurred with the group consensus to let > this story end > as of Jun 2013. > > I have. Just did put the NetWare bins up; go ahead and release. > > G�n. > > > > > > > > -- > Born in Roswell... married an alien... > http://emptyhammock.com/ --------------060901090809000005010607 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi

Oh I see - I had not realised this. In that case, I agree that sticking with 0.9.x is the only sensible option at this point in time :)

Mike

On 02/07/2013 14:35, Jeff Trawick wrote:
On Tue, Jul 2, 2013 at 8:53 AM, MikeM <michaelm12-asfbugzilla@aquaorange.net> wrote:
Hi,

Maybe the simple option is to do the final release with the old/existing bundled APR, but put a foot note in the release notes that the newer APR v1.4.8/1.5.2 has been confirmed to successfully work with 2.0.65. This way it may give confidence to anyone who is stuck on 2.0.x for some reason to use the newer APR/APR-util if needs be.

APR/APR-util 1.x won't work with httpd 2.0.x.  Someone continuing to use 2.0.x will need to hand-pick or backport fixes from apr/apr-util 0.9.x or later levels.  But then they'll have to backport fixes from httpd too.  The line was drawn at slightly different places for httpd vs. apr/apr-util, but the long term picture is the same: There is effort to remain on httpd 2.0.x if you want to pick up any code fixes, and the recommendation is clear.



Regards,
Mike


On 02/07/2013 13:06, Guenter Knauf wrote:
Hi Bill,
On 02.07.2013 01:47, wrowe@rowe-clan.net wrote:
I am not at all concerned
whether APR 0.9 is
released again or not since folks had years to take that up in our
discussions of
putting httpd 2.0 to bed, yet nobody so much as suggested a release,
nevermind some
volunteer to act on it.
true; but I thought that most of us probably forgot about that we bundle APR/APU with 2.0.x - like I did; the lack of APR/APU fixes came only to my attention when I was on building the 2.0.65 binaries ...
but since nobody else expressed an oppinion about then thats fine, and I shut up.

or if you have concurred with the group consensus to let this story end
as of Jun 2013.
I have. Just did put the NetWare bins up; go ahead and release.

Gün.







--
Born in Roswell... married an alien...
http://emptyhammock.com/

--------------060901090809000005010607--