> -----Original Message-----
> From: Rainer Jung <[email protected]>
> Sent: Thursday, March 15, 2018 12:09 PM
> To: [email protected]
> Subject: Re: [RESULT] [VOTE] Release httpd-2.4.32
> 
> Am 15.03.2018 um 17:34 schrieb Yann Ylavic:
> > On Thu, Mar 15, 2018 at 5:20 PM, Daniel Ruggeri <[email protected]>
> wrote:
> >>
> >> Personally, I would like to see *another* T&R (again, I volunteer and will
> >> see it through quickly) and no mention of this release be made public via
> >> ANNOUNCE.
> >> Thoughts?
> >
> > I think we should complete this release, with a warning somewhere for
> > mod_proxy_lb users on Windows. It's mirrored already.
> > Then we can provide 2.4.33 shortly.
> 
> +1 and s/mod_proxy_lb/mod_proxy_balancer/
> 
> Rainer

Agreed - once the mirrors have it... it's in the wild. I've been occupied the 
past few hours and have been mulling over this. WDYT about this verbiage? I'm 
poised and ready to send this and will do so in the next few hours if no 
additional feedback is given.



                Apache HTTP Server 2.4.32 Released

   March 15, 2018

   The Apache Software Foundation and the Apache HTTP Server Project
   are pleased to announce the release of version 2.4.32 of the Apache
   HTTP Server ("Apache").  This version of Apache is our latest GA
   release of the new generation 2.4.x branch of Apache HTTPD and
   represents fifteen years of innovation by the project, and is
   recommended over all previous releases. This release of Apache is
   a security, feature, and bug fix release.

*** Changes here
   We consider this release to be the best version of Apache available for 
   non-Windows platforms, and encourage users of all prior versions to upgrade.
   
   Please note, a bug after shipping this release was discovered that prevents
   the server from starting on Windows when mod_proxy_balancer is used.
   This manifests in error message "AH01179: balancer slotmem_create failed."
   Windows users are encouraged to postpone upgrades until the 
soon-to-be-available
   2.4.33+ release is made.
*** End Changes

   Apache HTTP Server 2.4.32 is available for download from:

     http://httpd.apache.org/download.cgi

   Apache 2.4 offers numerous enhancements, improvements, and performance
   boosts over the 2.2 codebase.  For an overview of new features
   introduced since 2.4 please see:

     http://httpd.apache.org/docs/trunk/new_features_2_4.html

   Please see the CHANGES_2.4 file, linked from the download page, for a
   full list of changes. A condensed list, CHANGES_2.4.32 includes only
   those changes introduced since the prior 2.4 release.  A summary of all 
   of the security vulnerabilities addressed in this and earlier releases 
   is available:

     http://httpd.apache.org/security/vulnerabilities_24.html

   This release requires the Apache Portable Runtime (APR), minimum
   version 1.5.x, and APR-Util, minimum version 1.5.x. Some features may
   require the 1.6.x version of both APR and APR-Util. The APR libraries
   must be upgraded for all features of httpd to operate correctly.

   This release builds on and extends the Apache 2.2 API.  Modules written
   for Apache 2.2 will need to be recompiled in order to run with Apache
   2.4, and require minimal or no source code changes.

     http://svn.apache.org/repos/asf/httpd/httpd/trunk/VERSIONING

   When upgrading or installing this version of Apache, please bear in mind
   that if you intend to use Apache with one of the threaded MPMs (other
   than the Prefork MPM), you must ensure that any modules you will be
   using (and the libraries they depend on) are thread-safe.

   Please note that while the Apache HTTP Server Project may publish some
   security patches to the 2.2.x flavor through at least December of 2017,
   no further maintenance patches of 2.2.x will be considered and no further
   releases will be distributed. The 2.2.x branch has now reached the end of
   its maintenance, and users are strongly encouraged to promptly complete
   their transitions to this 2.4.x flavor of httpd to benefit from security
   and bug fixes, as well as new features.

-- 
Daniel Ruggeri

Reply via email to