On Fri, Apr 1, 2016 at 11:49 AM, Yann Ylavic <ylavic....@gmail.com> wrote:
> On Fri, Apr 1, 2016 at 6:36 PM, Luca Toscano <toscano.l...@gmail.com> > wrote: > > > > +1, let's concentrate on 2.4 :) > > You know, there is still many 2.2 around, and some people may have > backported 2.4 fixes to 2.2 and decide to propose them some days. > If three PMC members (at least) think a 2.2.32 is worth it, it may > well be out ;) > As an RM of many 2.2 releases, my inclination at this point is to wait for the point where we have 'something to fix' (vis a vis Security patches) and hold a vote to announce at the same time that we are starting a 12 month EOL clock, broadcast widely with a 2.2.32 security release. That could happen at any point, but the amount of activity on 2.2 branch since the last release doesn't seem to merit a parallel release with 2.4.20 this coming week. Just my 2c... > But I agree that we should mainly reference 2.4 in the "generic" docs. > We actually have an http://httpd.apache.org/docs/current/ tree that reflects the now-current release, and needs not be changed when we finally release a 2.6 or 3.0 flavor.
