On Fri, Aug 30, 2002 at 11:10:27AM -0500, William A. Rowe, Jr. wrote: > I don't think we have enough -user- community to continue development > on any Apache 2.x. UNLESS we reconsider what we are doing wrong. > Breaking our users on every bugfix/point release would be a good start. > Seeing the successful completion of the PHP/Perl compatibility would > be a good finish.
I have to throw my two cents in here. I completely agree with this. Speaking as a system administrator and web administration consultant for quite a few companies, I have to say that I do not currently, and will never, use 2.0 for more than trivial applications, until I feel that I can rely on its (developmental) stability. I still reccomend to all of my clients that they use 1.3, and I expect to continue to do this for quite a long time unless folks here can resolve this issue adequately. I cannot afford to use a server where any time I try to upgrade it for a bugfix I might have to rewrite my configuration files, tweak all my add-on modules, or otherwise spend potentially days figuring out what's changed and why my server doesn't work the way it used to anymore, when all I wanted was a security fix. I know that most new 2.0 releases aren't quite this drastic, but the problem is that there's always the _possibility_ lurking there, and I can't afford to take the gamble on the 40 or 50 servers I'm (directly or indirectly) responsible for. I don't really care (from a user perspective) whether there's a 2.1 or not. It really doesn't matter. I don't care about all the nifty new features people are wanting to add to the project, because they're all going into a product which I'm not gonna be able to use, so they don't matter either. As far as I'm concerned 2.0 doesn't even exist yet, and won't until this situation is fixed. Until then, 1.3 is still the only Apache server there is. I really hope this situation changes because I really would like to start using 2.0 more. -alex
