From: "Chuck Murcko" <[EMAIL PROTECTED]>
Sent: Monday, April 30, 2001 11:12 AM


> I think we also need to deal with this issue, since being "back in the 
> core" is only temporary AFAICS. If we develop a mechanism for 
> reintegrating at release time, it can be the prototype for other modules.

++1, but I thought the consensus saiz nobody has the time to invest in this
aspect.  If I'm wrong, thank goodness :-)


> On Monday, April 30, 2001, at 09:10 AM, William A. Rowe, Jr. wrote:
> 
> > 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" <[EMAIL PROTECTED]>
> > To: "Apache Developers List" <[EMAIL PROTECTED]>
> > 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
> >> --
> >> -----------------------------------------
> >> [EMAIL PROTECTED] "There's a moon
> >> over Bourbon Street
> >> tonight..."
> >>
> >>
> >>
> >
> >
> >
> 
> Chuck Murcko
> Topsail Group
> http://www.topsail.org/
> 


Reply via email to