@Alex: please share your issue Le 21 janv. 2013 08:24, "Alex The Rocker" <[email protected]> a écrit :
> If I may: > > I agree with David's proposal to have a 1.5.2 dedicated to bug fixes, with > 1.6.0 being for enhancements. Our company's product fails with current > 1.5.2 snapshots (while it works with 1.5.1 GA), something to do with JAX-RS > but it could be related to JAXB changes, not sure yet. > > @David : do you have a link to a 1.5.2 snapshot which could be close to > what you plan for 1.5.2 ? > > Thanks, > Alex > > > > On Mon, Jan 21, 2013 at 8:19 AM, David Blevins <[email protected] > >wrote: > > > I'm starting to wonder if the JAXB changes I did aren't too large for a > > 1.5.2. In fact, I'm pretty confident they are. As well the OWB proxy > > changes are *definitely* beyond any definition of maintenance release. > > > > Maybe we want to cut a 1.5.2 with the code as of 2 weeks ago -- or now > > with some rollbacks. Then plan for a 1.6 and focus the announcement > around > > the various performance improvements in it -- faster CDI invocations, > > faster startup, anything else we can cram in... > > > > The dot releases don't get much media coverage, but pulling a few goodies > > out of 1.5.2 definitely does the trick. > > > > If we release 1.5.2 basically now, that buys us a month or more to work > in > > the CDI perf changes plus it shows continued stability/maturity. > > > > > > Happy to do the release work if people think it's a good idea. > > > > > > -David > > > > On Jan 20, 2013, at 10:55 PM, Jean-Louis MONTEIRO <[email protected]> > > wrote: > > > > > Are we ready to release before next month? > > > > > > As per the process and as we wanna wait for the improved OWB, maybe we > > can > > > revert on trunk to 34 and wait until the 36 is out. > > > > > > In my opinion, the biggest changes are in OWB, so let's work on OWB > > > integeration. > > > Tomcat 36 should not be that difficult to integrate. > > > > > > JLouis > > > > > > > > > 2013/1/19 Romain Manni-Bucau <[email protected]> > > > > > >> Hi guys, > > >> > > >> what's the plan? > > >> > > >> 1) we fix it (the fix is easy but need to be done on tomcat itself) - > > easy > > >> to do but not from our own code > > >> 2) we wait for 7.0.36 (next month i think) > > >> 3) we go back on 7.0.34 > > >> > > >> *Romain Manni-Bucau* > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > >> *Blog: **http://rmannibucau.wordpress.com/*< > > >> http://rmannibucau.wordpress.com/> > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > >> *Github: https://github.com/rmannibucau* > > >> > > >> > > >> > > >> ---------- Forwarded message ---------- > > >> From: Jess Holle <[email protected]> > > >> Date: 2013/1/18 > > >> Subject: Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35 > > >> To: Tomcat Developers List <[email protected]> > > >> Cc: Mark Thomas <[email protected]> > > >> > > >> > > >> 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 <[email protected]> > > 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< > > >> 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 > > >> > > > > > > > > > > > > -- > > > Jean-Louis > > > > >
