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 30624629C for ; Sat, 18 Jun 2011 12:45:02 +0000 (UTC) Received: (qmail 13810 invoked by uid 500); 18 Jun 2011 12:44:56 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 13744 invoked by uid 500); 18 Jun 2011 12:44:55 -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 13736 invoked by uid 99); 18 Jun 2011 12:44:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Jun 2011 12:44:55 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [188.40.99.202] (HELO eru.sfritsch.de) (188.40.99.202) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Jun 2011 12:44:49 +0000 Received: from [10.1.1.6] (helo=k.localnet) by eru.sfritsch.de with esmtp (Exim 4.69) (envelope-from ) id 1QXut1-000690-Cr for dev@httpd.apache.org; Sat, 18 Jun 2011 14:44:27 +0200 From: Stefan Fritsch To: dev@httpd.apache.org Subject: Re: Time for httpd 2.3.13...? And 2.4.0?? Date: Sat, 18 Jun 2011 14:44:26 +0200 User-Agent: KMail/1.13.7 (Linux/2.6.39-2-amd64; KDE/4.6.3; x86_64; ; ) References: <9369B9B4-B4CD-4318-9626-3334433AAD99@jaguNET.com> <4DFB89EE.40405@rowe-clan.net> In-Reply-To: <4DFB89EE.40405@rowe-clan.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201106181444.26721.sf@sfritsch.de> On Friday 17 June 2011, William A. Rowe Jr. wrote: > On 6/17/2011 6:39 AM, Jim Jagielski wrote: > > Are we ready for the next beta release??? > > > > And Maybe Even The Next Release being GA?? > > 2.3.13 soon, I'll fix the mod_ldap load ordering quirk on Sunday > and just do a bit more validation with apr trunk. I am currently working on limiting the parallel connections per process on MPM event (see STATUS). I would really like to have this in 2.3.13, but I hope I will be able to finish it until tomorrow. > The Next Release? I'm not seeing enough activity on users@ and not > even seeing current ASF infra updated enough to justify that ;-) > But if 2.2.13 proves rock solid, maybe the subsequent release? +1 to 2.3.13 as beta. Then hopefully the next release can be GA.