Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4A01F260.2050908@rowe-clan.net>
Date: Wed, 06 May 2009 15:26:08 -0500
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: mod_proxy hooks for clustering and load balancing
References: <4239a4320905061126n6b851f1g8f61dbb6b0f84756@mail.gmail.com>
 <7B68FC76-F21F-4574-9B4D-320F28197E7C@jaguNET.com>
 <4239a4320905061153l7ec0f181j18cfdd663c856d5d@mail.gmail.com>
 <863146C9-B736-4022-8BE2-F42BAF1D305D@jaguNET.com>
 <4A01F110.7030001@sharp.fm>
In-Reply-To: <4A01F110.7030001@sharp.fm>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Graham Leggett wrote:
> Jim Jagielski wrote:
> 
>> I'll stop worrying about 2.2 when 2.4 comes closer to being a reality.
>>
>> Not saying that releasing 2.4 isn't worth it, but there have been stops and
>> starts all along the way, and I think we need to be clear on what we
>> expect 2.4 to be. Until then, we have no clear defining line on when
>> 2.4 is "done."
> 
> Is there anything additional that we want v2.4 to do over and above what
> it does now?

Conversely, anything that isn't done correctly yet in v2.4 that must be
refactored, or anything that is done in v2.4 that we simply wouldn't want
to release with 2.4.0?