Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of jim@jagunet.com designates
 209.133.199.10 as permitted sender)
Message-Id: <A7101F00-6178-47AD-80FB-F217CB041C2F@jaguNET.com>
From: Jim Jagielski <jim@jaguNET.com>
To: dev@httpd.apache.org
In-Reply-To: <49302488.5000002@force-elite.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Intent to Roll 2.3.0-alpha
Date: Sat, 29 Nov 2008 10:39:34 -0500
References: <49302488.5000002@force-elite.com>


On Nov 28, 2008, at 12:04 PM, Paul Querna wrote:

> Hi dev@,
>
> FYI, I intend to roll 2.3.0-alpha, our first release from trunk in  
> about  3 years, on Saturday December 6th.
>
> As in the previous 2.${odd} release cycles, this is not a stable  
> release, do not guarantee a stable ABI, and would not be recommended  
> for production usage:
> <https://svn.apache.org/repos/asf/httpd/httpd/trunk/VERSIONING>
>
> I think we need to start stabilizing trunk, and getting on the path  
> of doing 2.4.x 'soon'.
>
> In other words, if you wanted some big ass feature in 2.4, start  
> coding now, your time is short :D
>

I will be adding at least 2 new hooks to mod_proxy...

Plus, I'd like for the monitor hook to take some useful arguments
rather than just a pool :) :)