httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: [users@httpd] Stable Release of Apache
Date Thu, 11 Jun 2009 19:33:22 GMT
Tom Evans wrote:
> On Thu, 2009-06-11 at 07:57 -0700, Mohit Anchlia wrote:
>> I see that apache 2.2.11 has been released but how do I find out if
>> that's a stable release and something I can consider deploying in
>> production?
> All releases of apache are stable releases; that is the definition of a
> release. The apache project don't release the unstable versions (eg the
> 2.1 and 2.3 branches).

Well, mostly correct.  We do 'release' 2.1, 2.3 branches (development or
unstable, as you call it) by identifying them as -alpha or -beta.

There would be no 'stable' -alpha or -beta designations, when the branch
reaches maturity, it is given the next even-numbered revision, e.g. 2.4
or 3.0, and won't be identified as either -alpha or -beta.

OR quoting the web site...

"The Apache HTTP Server Project is proud to announce the release of version
2.2.11 of the Apache HTTP Server ("Apache"). This version is principally a
bugfix release."

"This version of Apache is a major release and the start of a new stable
branch, and represents the best available version of Apache HTTP Server. New
features include Smart Filtering, Improved Caching, AJP Proxy, Proxy Load
Balancing, Graceful Shutdown support, Large File Support, the Event MPM, and
refactored Authentication/Authorization."

I guess it's a little misleading, 2.2 certainly isn't "new" anymore, and
quoting the actual 2.2.11 announcement file;

"The Apache Software Foundation and the Apache HTTP Server Project are
pleased to announce the release of version 2.2.11 of the Apache HTTP Server

"This version of Apache is principally a bug fix release."

"We consider this release to be the best version of Apache available, and
encourage users of all prior versions to upgrade."

So there's the message that should actually be on the main site :)  cc'ing
docs@ so they can take a look at this and contribute an appropriate solution
to the confusion.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message