Sapan J . Bhatia wrote: > The HTTPD Project signed off today on the 2.0.35 release, and recommends it > for use on production websites. 2.0.35 is now considered our best release > and should be used in preference to all older versions (including the 1.3 > series).
Ok I accept it maybe it is ready for production use. Since Sapan has been so adamant on documented proof. Here is the article on which I was raving and ranting. http://www.apacheweek.com/issues/02-02-08 I admit I should be checking more thoroughly before blabering. But if you read the complete article it specifically says 2.0.31 (I wonder how much changed between 2.0.31 and 2.0.35 - the version number suggest probably next to nothing) is in a alpha stage. From alpha to production ready in 2 months is something of a miracle I would have to admit considering the size of the project. If you also read the section about stability of apache 2.0.31 it says <qoute> Another answer, however, is that the quality is taking so long to achieve because the codebase keeps getting destabilised. It seems as though basic underlying subsystems keep getting modified, frequently in a significant way, on a monthly if not weekly basis. Perturbations from these changes ripple through the rest of the server, and it often takes weeks for the last temblors to subside. </quote> If you read my first reply I specifically said it is changing too much and too fast which was inspired by this particular article. > To end this, I still think 2.0.35, and Apache 2.0 in general is a great Uhh I never ever said apache is not a good product. I just said the latest version might need some more time to settle down before one goes for updating production servers. For testing purposes it probably was ready long time ago. In any case I would like to appologize if anyone felt I implied apache wasnt a good software but I wouldnt recommend anyone to use 2.0.35 on a production server right now as in today. Mithun ================================================ To subscribe, send email to [EMAIL PROTECTED] with subscribe in subject header To unsubscribe, send email to [EMAIL PROTECTED] with unsubscribe in subject header Archives are available at http://www.mail-archive.com/ilugd%40wpaa.org =================================================
