Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Message-ID: <030901c0d176$fb7c0910$96c0b0d0@roweclan.net>
From: "William A. Rowe, Jr." <wrowe@covalent.net>
To: <new-httpd@apache.org>
References: <3AEB00BA.23FF860C@sharp.fm>
Subject: Re: Apache rollup tree
Date: Mon, 30 Apr 2001 08:10:00 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I thought the consensus is to roll in the known-stable proxy back
into httpd-2.0/modules/proxy.  Little sense in keeping three trees.
Did I miss something?

----- Original Message ----- 
From: "Graham Leggett" <minfrin@sharp.fm>
To: "Apache Developers List" <new-httpd@apache.org>
Sent: Saturday, April 28, 2001 12:41 PM
Subject: Apache rollup tree


> Hi all,
> 
> After the whole integrate-mod-proxy discussion died down, much was
> suggested about a rolldown tree where the latest stable version of a
> module was available when an RM wanted to make a release of Apache. This
> would require two steps:
> 
> - the mod_proxy people (us) would need to create a directory underneath
> the proxy CVS tree to contain the most recent stable known-to-work
> release of the module (eg. proxy/stable). (This directory would at the
> moment be empty until our showstopper bugs are fixed).
> 
> - the how-to-roll-Apache page would need to be updated to include
> instructions on where to pull this proxy code, and where to place it in
> the release directory structure (modules/proxy). (In time, other modules
> would need to go through the same procedure, if this gets out of hand,
> we can automate it).
> 
> I can do the first bit, votes for the second?
> 
> Regards,
> Graham
> -- 
> -----------------------------------------
> minfrin@sharp.fm "There's a moon
> over Bourbon Street
> tonight..."
> 
> 
>