You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mark Thomas <ma...@apache.org> on 2013/01/11 00:40:29 UTC
[VOTE] Release Apache Tomcat 7.0.35
The proposed Apache Tomcat 7.0.35 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.35/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-123/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_35/
The proposed 7.0.35 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.35 Stable
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.35
Posted by Konstantin Kolinko <kn...@gmail.com>.
2013/1/11 Mark Thomas <ma...@apache.org>:
> The proposed Apache Tomcat 7.0.35 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.35/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-123/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_35/
>
> The proposed 7.0.35 release is:
> [ ] Broken - do not release
> [x] Stable - go ahead and release as 7.0.35 Stable
Testsuite passes successfully, on WinXP JDK 6u38 32-bit, BIO,NIO,APR
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.35
Posted by Rainer Jung <ra...@kippdata.de>.
On 11.01.2013 00:40, Mark Thomas wrote:
> The proposed Apache Tomcat 7.0.35 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.35/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-123/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_35/
>
> The proposed 7.0.35 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.35 Stable
+1 to release.
Details:
- MD5 OK
- signatures OK
- key in KEYS file
- gz and zip for src and bin consistent
- src completely consistent with svn tag
Except for executable bits on Tester.java in svn.
Not critical, already fixed for next release.
- builds fine
- new warning in
test/org/apache/catalina/core/TestStandardContextResources.java:
uses unchecked or unsafe operations
- build result looks consistent with binaries
- no checkstyle complaints
- some Javadoc warnings (only in jdbc-pool, not a regression)
- Unit tests
- no error or failures
- some warnings (see below), one new warning type
concerning NPE in CoyoteAdapter when calling access log
- JMX MBean-Comparison OK
- OpenFileDescriptorCount down from 61 to 57
Build and tests were done using Java 1.6.0_37. OS was Solaris 10 Sparc,
tcnative was 1.1.24 based on APR 1.4.6 and OpenSSL 1.0.1c (plus two
patches).
Unit test warnings (except for tribes and the access log exceptions all
of those look like 7.0.33 and
before):
- Exception while attempting to add an entry to the access log
in org.apache.catalina.connector.CoyoteAdapter log
while running org.apache.el.TestELInJsp and
org.apache.jasper.compiler.TestParser.
The exception stack in both cases was:
java.lang.NullPointerException
at org.apache.catalina.connector.CoyoteAdapter.log(CoyoteAdapter.java:511)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1033)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1680)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Line 511 in CoyoteAdapter is
connector.getService().getContainer().logAccess(...);
- org.apache.catalina.deploy.TestWebXmlOrdering
- BIO, NIO and APR: [main]
org.apache.catalina.deploy.WebXml.orderWebFragments Used a wrong
fragment name z at web.xml absolute-ordering tag!
- org.apache.tomcat.util.net.TestCustomSsl
- BIO twice "Exception getting SSL attributes"
in org.apache.coyote.http11.Http11Processor actionInternal
exception is:
javax.net.ssl.SSLProtocolException: handshake alert: no_certificate
- NIO twice "WARNING: Exception re-negotiating SSL connection"
in org.apache.coyote.http11.Http11NioProcessor actionInternal
- tribes: several warnings, roughly same as before
Unit test SEVERE messages: 225 total (+7), about 35 unique messages
Most of those are of type "Servlet.service() for servlet ... threw
exception" (134 times). 3 less not stopped threads errors, some deltas
in tribes errors, 3 times each of the new messages
WebXml.mergeLifecycleCallback The [Post Construct Methods] with name [a]
was defined inconsistently in multiple fragments including fragment with
name [null] located at [null]
and
WebXml.mergeLifecycleCallback The [Pre Destroy Methods] with name [b]
was defined inconsistently in multiple fragments including fragment with
name [null] located at [null]
and twice the new
Error processing request
with reason an NPE:
java.lang.NullPointerException
at
org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSelector.java:129)
at
org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.java:174)
at
org.apache.coyote.http11.InternalNioOutputBuffer.writeToSocket(InternalNioOutputBuffer.java:163)
at
org.apache.coyote.http11.InternalNioOutputBuffer.flushBuffer(InternalNioOutputBuffer.java:242)
at
org.apache.coyote.http11.InternalNioOutputBuffer.endRequest(InternalNioOutputBuffer.java:121)
at
org.apache.coyote.http11.AbstractHttp11Processor.action(AbstractHttp11Processor.java:749)
at org.apache.coyote.Response.action(Response.java:173)
at org.apache.coyote.Response.finish(Response.java:279)
at
org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:293)
at
org.apache.catalina.connector.Response.finishResponse(Response.java:513)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:434)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1680)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Exception" in output of unit tests: 220 times (+11), of these 75 times
"javax.servlet.ServletException: Opps."
I'm not claiming that any of the SEVERE or Exception messages are
important. Total numbers of warnings, SEVERE and exceptions are
slightly larger than for previous releases.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.35
Posted by Konstantin Kolinko <kn...@gmail.com>.
2013/1/11 Mark Thomas <ma...@apache.org>:
> The proposed Apache Tomcat 7.0.35 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.35/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-123/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_35/
>
It was reported on the users list that tomcat-embed-jasper.pom
references wrong version of ecj.
http://markmail.org/message/tpv35gf3mq7btkyk
I corrected this in
http://svn.apache.org/viewvc?view=revision&revision=1431922
I have not added it to the changelog yet, and maybe we need a better
fix to substitute that number at build time.
I would be OK if this were fixed by re-uploading files to maven
without regenerating the binaries.
Otherwise I'd better wait for 7.0.36: it should not be far away, and
current version should still be able to run with older ECJ.
The testing goes fine thus far.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Fwd: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
No 1.5.2 quickly and preparing 1.6.0 for the upcoming weeks (let's say in
February or so)
2013/1/21 Romain Manni-Bucau <rm...@gmail.com>
> guys, does it mean we release both 1.5.2 and 1.6.0 at the same time?
>
> *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*
>
>
>
> 2013/1/21 middleware <da...@infocamere.it>
>
> > >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...
> >
> > Agree 100%
> >
> > Frequent releases are important, but it's even more important they are
> are
> > stable, very well tested and with big changes highlighted by a change in
> > the
> > second digit of the version.
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://openejb.979440.n4.nabble.com/Fwd-RESULT-VOTE-Release-Apache-Tomcat-7-0-35-tp4660311p4660330.html
> > Sent from the OpenEJB Dev mailing list archive at Nabble.com.
> >
>
--
Jean-Louis
Re: Fwd: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Romain Manni-Bucau <rm...@gmail.com>.
guys, does it mean we release both 1.5.2 and 1.6.0 at the same time?
*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*
2013/1/21 middleware <da...@infocamere.it>
> >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...
>
> Agree 100%
>
> Frequent releases are important, but it's even more important they are are
> stable, very well tested and with big changes highlighted by a change in
> the
> second digit of the version.
>
>
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Fwd-RESULT-VOTE-Release-Apache-Tomcat-7-0-35-tp4660311p4660330.html
> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>
Re: Fwd: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by middleware <da...@infocamere.it>.
>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...
Agree 100%
Frequent releases are important, but it's even more important they are are
stable, very well tested and with big changes highlighted by a change in the
second digit of the version.
--
View this message in context: http://openejb.979440.n4.nabble.com/Fwd-RESULT-VOTE-Release-Apache-Tomcat-7-0-35-tp4660311p4660330.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Romain Manni-Bucau <rm...@gmail.com>.
@Alex: please share your issue
Le 21 janv. 2013 08:24, "Alex The Rocker" <al...@gmail.com> 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 <david.blevins@gmail.com
> >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 <je...@gmail.com>
> > 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 <rm...@gmail.com>
> > >
> > >> 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 <je...@ptc.com>
> > >> Date: 2013/1/18
> > >> Subject: Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
> > >> To: Tomcat Developers List <de...@tomcat.apache.org>
> > >> Cc: Mark Thomas <ma...@apache.org>
> > >>
> > >>
> > >> 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<
> > >> 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
> >
> >
>
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Alex The Rocker <al...@gmail.com>.
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 <da...@gmail.com>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 <je...@gmail.com>
> 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 <rm...@gmail.com>
> >
> >> 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 <je...@ptc.com>
> >> Date: 2013/1/18
> >> Subject: Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
> >> To: Tomcat Developers List <de...@tomcat.apache.org>
> >> Cc: Mark Thomas <ma...@apache.org>
> >>
> >>
> >> 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<
> >> 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
>
>
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Jacek Laskowski <ja...@japila.pl>.
On Mon, Jan 21, 2013 at 8:19 AM, David Blevins <da...@gmail.com> wrote:
> Happy to do the release work if people think it's a good idea.
It sounds like a very good plan. I like the idea to stick with 1.5.x
for minor changes and 1.6 for something bigger.
I must admit that you're really doing a great job with the versioning
and...public relations! :-)
Jacek
--
Jacek Laskowski
Functional languages (Clojure), Java EE, and IBM WebSphere -
http://blog.japila.pl
"Never discourage anyone who continually makes progress, no matter how
slow." Plato
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Since no revert is done on trunk all works for me (but we dont have owb
improvement atm, just bugfixes)
Le 21 janv. 2013 08:19, "David Blevins" <da...@gmail.com> a écrit :
> 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 <je...@gmail.com>
> 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 <rm...@gmail.com>
> >
> >> 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 <je...@ptc.com>
> >> Date: 2013/1/18
> >> Subject: Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
> >> To: Tomcat Developers List <de...@tomcat.apache.org>
> >> Cc: Mark Thomas <ma...@apache.org>
> >>
> >>
> >> 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<
> >> 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
>
>
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
Good reminder. Agree with the 1.6.0 in regards to the huge changes done.
Ok as well for a maintenance release 1.5.2.
JLouis
2013/1/21 David Blevins <da...@gmail.com>
> 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 <je...@gmail.com>
> 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 <rm...@gmail.com>
> >
> >> 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 <je...@ptc.com>
> >> Date: 2013/1/18
> >> Subject: Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
> >> To: Tomcat Developers List <de...@tomcat.apache.org>
> >> Cc: Mark Thomas <ma...@apache.org>
> >>
> >>
> >> 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<
> >> 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
>
>
--
Jean-Louis
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by David Blevins <da...@gmail.com>.
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 <je...@gmail.com> 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 <rm...@gmail.com>
>
>> 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 <je...@ptc.com>
>> Date: 2013/1/18
>> Subject: Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
>> To: Tomcat Developers List <de...@tomcat.apache.org>
>> Cc: Mark Thomas <ma...@apache.org>
>>
>>
>> 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<
>> 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
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
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 <rm...@gmail.com>
> 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 <je...@ptc.com>
> Date: 2013/1/18
> Subject: Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
> To: Tomcat Developers List <de...@tomcat.apache.org>
> Cc: Mark Thomas <ma...@apache.org>
>
>
> 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<
> 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
Fwd: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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 <je...@ptc.com>
Date: 2013/1/18
Subject: Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
To: Tomcat Developers List <de...@tomcat.apache.org>
Cc: Mark Thomas <ma...@apache.org>
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<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
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Jess Holle <je...@ptc.com>.
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
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Mark Thomas <ma...@apache.org>.
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.
It is less than 10 working days before I'd normally start the 7.0.36
release anyway and this month I am trying to keep more on top of the
bugs so the release is closer to the start of Feb than the middle of Feb.
A release isn't really that much work but I'd rather spend my time on
the WebSocket implementation. If there is a real need for 7.0.36 we
could pull it forward but I'm not seeing that right now.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Jeremy Boynes <jb...@apache.org>.
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[RESULT] [VOTE] Release Apache Tomcat 7.0.35
Posted by Mark Thomas <ma...@apache.org>.
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.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.35
Posted by Yoav Shapira <yo...@apache.org>.
On Thu, Jan 10, 2013 at 6:40 PM, Mark Thomas <ma...@apache.org> wrote:
> The proposed Apache Tomcat 7.0.35 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.35/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-123/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_35/
>
> The proposed 7.0.35 release is:
> [ ] Broken - do not release
> [ X ] Stable - go ahead and release as 7.0.35 Stable
No big issues found by me.
Yoav
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.35
Posted by Olivier Lamy <ol...@apache.org>.
2013/1/11 Mark Thomas <ma...@apache.org>:
> The proposed Apache Tomcat 7.0.35 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.35/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-123/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_35/
>
> The proposed 7.0.35 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.35 Stable
Tested artifacts with maven plugin and with applications.
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.35
Posted by Mark Thomas <ma...@apache.org>.
On 10/01/2013 23:40, Mark Thomas wrote:
> The proposed Apache Tomcat 7.0.35 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.35/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-123/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_35/
>
> The proposed 7.0.35 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.35 Stable
Unit tests pass on 64-bit Windows and 64-bit Linux
EL TCK passes
JSP TCK passes with HTTP (direct) BIO, NIO & APR/native (1.1.24)
Servlet TCK passes with
- HTTP (direct) BIO, NIO & APR/native (1.1.24)
- HTTP (mod_proxy_http) BIO, NIO & APR/native (1.1.24)
- AJP (mod_jk) BIO, NIO & APR/native (1.1.24)
- AJP (mod_proxy_ajp) BIO, NIO & APR/native (1.1.24)
All TCK tests run on 64-bit Linux with a security manager
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org