On 1/18/2013 3:13 PM, Mark Thomas wrote:
On 18/01/2013 19:32, Jeremy Boynes wrote:
On Wed, Jan 16, 2013 at 1:41 AM, Mark Thomas <ma...@apache.org> wrote:
Votes were as follows:
+1 (binding): kkolinko, rjung, yoavs, olamy, markt
No other votes were cast.
The vote therefore passes.
I'll publish the binaries and announce later today once the mirrors have
caught up.
Given the regression with issue 54440, should this be withdrawn and a
quick release of '36 be done?
https://issues.apache.org/bugzilla/show_bug.cgi?id=54440
I'm wasn't planning on it. If that bug is a showstopper then folks can
stick on 7.0.34 for a few more weeks.
Nothing in 7.0.35 is really that critical. For myself I went to 7.0.35,
swore furiously about the bug -- almost just dropped back to 7.0.34 but
then applied the patch and moved on.
I guess the real question is how many "new to Tomcat" folk are
realistically going to pick up 7.0.35 *and* jump to doing JSP
precompilation *and* do so before 7.0.36 is out. If they're /not /new
to Tomcat, then they know it *did* work and will start looking for where
it stopped, check the mailing lists, etc. If not and they hit this
issue before 7.0.36 is announced, then they'll just assume Tomcat is no
good -- but how many folk will really fall into that category?
--
Jess Holle
