Published December 2nd, 2005

I was the release manager for Apache HTTPD 2.2.0. I have to say, being the release manager was the hardest thing I have ever done for Apache HTTPD. I think now that the 2.2.x branch is started, it will hopefully be an easier task. This also means we have are 2.3-dev on /trunk/. I am hoping to find time to help with the improved async work on the Event MPM.

After 9 alphas and beta in the last year, 2.2 is the next ‘stable’ branch of Apache. Its a relatively easy jump from 2.0 too, but adds lots of new features. You should upgrade now.

We finally sent the release announcement yesterday. Coverage from the RSS Feeds and searches:

  • ZDNet (same article on Kinda weird quoting the announcement like it was a press release. They also mention the RFP for helping with the ASF’s Infrastructure.
  • Slashdot - Smattering of comments all over the board. Seems like most people do like the Large File Support. At least one person likes the new httpd -M option, which dumps all loaded modules. I think that feature will be one of the best for helping confused users.
  • Brad - says: ”Looks like most the stupid shit has been fixed:” Which, is a pretty good way to describe the 2.2 feature set. Lots of low hanging fruit fixes and features
  • collmmacc - No comments, but I will try to help increase his page rank.
  • JimJag - Notes that Apache 1.0.0 was released on the same day 10 years ago. Even if most of the original developers are no longer active, the project is still successful. I believe this is one of the most undervalued attributes of community, and hopefully other open source projects will learn that its the community that matters to long term success, not fighting over silly features.
  • Gentoo Bugzilla - Already have an open bug, requesting the ebuild.

A HUGE round of thanks to the many other Apache HTTP Server developers.

Written by Paul Querna, CTO @ ScaleFT. @pquerna