Just because it is released, doesn't mean we need to announce it. We
can easily release a quick 2.4.33 and announce *that*. 2.4.32 was/is
just an un-announced release.

> On Mar 15, 2018, at 2:51 PM, Christophe Jaillet 
> <[email protected]> wrote:
> 
> Le 15/03/2018 à 17:34, Yann Ylavic a écrit :
>> 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.
>> Regards,
>> Yann.
> 
> +1 as well for me.
> It's unfortunate but the release has been voted and is in the wild now.
> The best is to mitigate the announce as proposed by Yann and release a 
> 2.4.n+1 ASAP.
> 
> CJ
> 

Reply via email to