So it's my intent to fold the proxy back in before httpd release, unless there's a compelling reason not to. For now, we'll go ahead to cut milestone releases starting with the 2.0.24 tag. I wouldn't even call them beta, as that connotes remaining a separate project or release to me. They'll still have version numbers, though.
Like mid air refueling, merging proxy back into httpd will work best when both moving pieces are in sync; that's the tricky part.
If you or other folks think this is a nonoptimal way to proceed, let's discuss it further. I could be way off base here. Plus I don't always communicate what I think well (this sentence might just prove itself).
Chuck
On Monday, August 27, 2001, at 03:08 AM, Eli Marmor wrote:
Hi Chuck,
You wrote (before the vacation):
If things look good w/2.0.24 when I get back, I'll tag & cut a proxy release beta.
Are you going to do it soon?
It will be cool to have finally a stable (uhmmm - more or less...) version
of Apache 2, with proxy support. I believe it will be a step in the
direction of a full re-integration of mod_proxy in the standard source
tree of Apache (they can't veto forever...)
I know that the ASF members are not sure what to prefer as a beta (2.0.24,
2.0.24 + patches, 2.0.25, 2.0.24 for UNIX while WIN32 is still declared as
an alpha, etc.), but my experience hints me that it is not the best idea
to wait for their decision; If you make YOUR decision, I believe that all
of us will be behind of you ;-)
Chuck Murcko Topsail Group http://www.topsail.org/
