Re: Apache HTTP Server 2.1.2 tagged...
+1, lets get something out there for the community to test. If we have to go through a bunch of 2.1.x-betas before we feel comfortable with branching, so be it. Brad [EMAIL PROTECTED] Monday, December 13, 2004 4:30:29 PM --On Monday, December 13, 2004 2:40 PM -0700 Paul Querna [EMAIL PROTECTED] wrote: This would be 2.1.2-beta right? Not 2.2.0-beta1? Correct. Our first 'beta' release doesn't necessarily mean that it'd be 2.2.0-beta1. We can have as many 2.1.x betas as we want. However, I think it was said that the 2.2.0 branch will start with some 2.1.x beta - I just don't think we're quite at the branch point yet, but, IMHO, we should try to get some folks pounding on 2.1.x... -- justin
Re: Apache HTTP Server 2.1.2 tagged...
At 07:28 PM 12/12/2004, Paul Querna wrote: +1 for promoting it to beta status. I tested on NetBSD-2.0 and FreeBSD 5.2.1. I was able to duplicate the regressions in mod_rewrite and mod_proxy: http://issues.apache.org/bugzilla/show_bug.cgi?id=32459 However, the proxy related regressions are only a small part of the code. I believe we need a beta release to help find other issues. -0 right now on beta, here's my thinking; Apache 2.0 didn't (originally) deliver a functioning cache or proxy. That was the #1 reason for folks to 'choose' to hang onto 1.3 when the 2.0 server went out the door. Delivering Beta 1 with a fully functioning cache and proxy would go a huge ways in giving beta testers (as opposed to dev alpha hackers) some strong faith in the 2.2 release. Because cache and proxy were the #1 hurdle last time around, shipping Beta 1 with bugs in either module would not provide much street credibility. Bill
Re: Apache HTTP Server 2.1.2 tagged...
Paul Querna wrote: +1 for promoting it to beta status. +1 for making it beta.. time to get some more people to shake the bugs out. been using it on OS/X for a while now and it seems not to crash every 5 seconds ;-) Ian
Re: Apache HTTP Server 2.1.2 tagged...
William A. Rowe, Jr. wrote: -0 right now on beta, here's my thinking; Apache 2.0 didn't (originally) deliver a functioning cache or proxy. That was the #1 reason for folks to 'choose' to hang onto 1.3 when the 2.0 server went out the door. Delivering Beta 1 with a fully functioning cache and proxy would go a huge ways in giving beta testers (as opposed to dev alpha hackers) some strong faith in the 2.2 release. This would be 2.1.2-beta right? Not 2.2.0-beta1? This was my understanding. Making it 2.1.2-beta would allow placing of it on the httpd.a.o frontpage. Correct? I agree if we were to call it 2.2.0-beta1, these types of bugs should be a show stopper. -Paul
Re: Apache HTTP Server 2.1.2 tagged...
--On Monday, December 13, 2004 2:40 PM -0700 Paul Querna [EMAIL PROTECTED] wrote: This would be 2.1.2-beta right? Not 2.2.0-beta1? Correct. Our first 'beta' release doesn't necessarily mean that it'd be 2.2.0-beta1. We can have as many 2.1.x betas as we want. However, I think it was said that the 2.2.0 branch will start with some 2.1.x beta - I just don't think we're quite at the branch point yet, but, IMHO, we should try to get some folks pounding on 2.1.x... -- justin
Re: Apache HTTP Server 2.1.2 tagged...
Ian Holsman wrote: Paul Querna wrote: +1 for promoting it to beta status. +1 for making it beta.. time to get some more people to shake the bugs out. been using it on OS/X for a while now and it seems not to crash every 5 seconds ;-) Ian . OS/X? N.
Re: Apache HTTP Server 2.1.2 tagged...
+1 for promoting it to beta status. I tested on NetBSD-2.0 and FreeBSD 5.2.1. I was able to duplicate the regressions in mod_rewrite and mod_proxy: http://issues.apache.org/bugzilla/show_bug.cgi?id=32459 However, the proxy related regressions are only a small part of the code. I believe we need a beta release to help find other issues. -Paul Justin Erenkrantz wrote: In the continuing string of 2.1.x releases, Apache HTTP Server 2.1.2 is now available at: http://httpd.apache.org/dev/dist/ Currently, this is only an alpha-quality release and is only meant for developers to provide feedback for the upcoming 2.2 series. New features with the 2.1/2.2 series are listed here: http://httpd.apache.org/docs-2.1/new_features_2_2.html Changes are here: http://httpd.apache.org/dev/dist/CHANGES_2.1 Please provide feedback, votes, etc. If you have any problems, as always, please bring them up on [EMAIL PROTECTED] Thanks! -- justin
Re: Apache HTTP Server 2.1.2 tagged...
httpd builds on NetWare but we are having problems with the version of APR that was included in the tarball. APR 1.0.1 is failing to build on the latest LibC SDK on NetWare due to a couple of minor type mismatches. It requires the following patch from the APR 1.0.x branch: threadproc\netware\proc.c locks\netware\thread_mutex.c -r106967 Is a new revision of APR 1.0.x going to be released anytime soon? Brad [EMAIL PROTECTED] Thursday, December 09, 2004 1:29:37 AM In the continuing string of 2.1.x releases, Apache HTTP Server 2.1.2 is now available at: http://httpd.apache.org/dev/dist/ Currently, this is only an alpha-quality release and is only meant for developers to provide feedback for the upcoming 2.2 series. New features with the 2.1/2.2 series are listed here: http://httpd.apache.org/docs-2.1/new_features_2_2.html Changes are here: http://httpd.apache.org/dev/dist/CHANGES_2.1 Please provide feedback, votes, etc. If you have any problems, as always, please bring them up on [EMAIL PROTECTED] Thanks! -- justin
Re: Apache HTTP Server 2.1.2 tagged...
--On Thursday, December 9, 2004 11:03 AM -0700 Brad Nicholes [EMAIL PROTECTED] wrote: Is a new revision of APR 1.0.x going to be released anytime soon? I don't see anything in the CHANGES entry for 1.0.2 in APR. *nudge* -- justin
