Apache May Stop 1.3, 2.0 Series Releases 77
Dan Jones writes "The Apache Software Foundation may stop releasing new versions of the older 1.3 and 2.0 series of its flagship Web server product with most development now focused on the 2.2 series. Nothing is final yet, but messages to the Apache httpd developer mailing list recommend the formal deprecation of the 1.3.x branch, with most citing a lack of development activity. The Apache HTTP server project is one of the most successful and popular open source projects and has become an integral part of the technology stack for thousands of Web and SaaS applications. The first generation of Apache was released in 1995, and the 2.0 series began in 2002. Apache httpd 2.2 began in 2005, with the latest release (October 2009) being 2.2.14. However, the most recent releases of the 1.3 and 2.0 series servers were back in January 2008. With the combined total of active 1.3 and 2.0 series Apache Web servers well into the millions, any decision to end-of-life either product will be watched closely."
Re:about time (Score:3, Informative)
Right. Upgrade to a modern HTTP server like Nginx http://www.nginx.net/ [nginx.net] or Lighttpd, you won't regret it.
And if for some reason you really need Apache 1.3.x, this code is maintained by OpenBSD and an enhanced version is shipped with the OS.
Re:Surly this is just a formality (Score:5, Informative)
As per http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x/README [apache.org] , the proposal (Full disclosure: I'm colm@apache.org - the proposer), was that we would start distributing security patches via;
http://www.apache.org/dist/httpd/patches/ [apache.org]
The main point is to reduce the overhead and burden of creating full releases. Releases take a large amount of community involvement and time, and are becoming impractical. The 1.3.x branch does not even build on many modern platforms - for example the configure script is incompatible with dash and there is a getline() function which conflicts with a glibc neologism.
Hope that helps.
Re:about time (Score:1, Informative)
The problem is that nginx does not support IPv6 which is kind if sad for a "modern" HTTP server.
Not sure what universe in which you reside, but in this one nginx has supported IPv6 since 0.7.36, released in 21 Feb 2009.
Sauce: http://nginx.net/CHANGES-0.7
Re:Netcraft confirms... (Score:2, Informative)