Jim Jagielski wrote:
Plus, every 3 months would coincide with the report-to-board cycle,
making it easier for everyone to follow :) Next is due in May, so
if we release this month, then we can follow a "Release before
the board report" or else "Release at board report" cycle (with
the caveat I noted before ;) )
As noted (and as I pinged a few people about in Amsterdam), I'm
looking to push for a 2.2.9 soon. We have enough for sure
warrant it... There is the "ship 1.3.0 with 2.2.9" thread going on,
but I do not want 2.2.9 to hold off too long for that...
So I'd like to propose 2.2.9 for the end of this month.
Sorry to butt in, but is there any hope of getting issue #44803
addressed in that timeframe?
[The gap between mod_jk and mod_proxy_ajp in this and other areas (I
don't believe it can set a longer packet size than 8K yet) is a bit
troubling...]
--
Jess Holle
