Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-18 Thread Mark Thomas
On 12/12/2018 13:22, Mark Thomas wrote: > The proposed 8.5.37 release is: > [ ] Broken - do not release > [X] Stable - go ahead and release as 8.5.37 Unit tests passed for NIO, NIO2 and APR/native on OSX, Linux and Windows with Tomcat Native 1.2.19 built with APR 1.6.5 and OpenSSL 1.1.1a Mark

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-18 Thread Mark Thomas
On 18/12/2018 00:03, Emmanuel Bourg wrote: > I've tested on Debian Sid with OpenJDK 11.0.1+13 and OpenSSL 1.1.1a, and > I've noticed two test failures in TestClientCertTls13 with the three > connectors. Is this expected? No. It looks like a fix to the tests didn't get back-ported correctly.

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-17 Thread Emmanuel Bourg
Le 12/12/2018 à 14:22, Mark Thomas a écrit : > The proposed Apache Tomcat 8.5.37 release is now available for voting. > > The major changes compared to the 8.5.35 release are: > > - Implement the requirements of section 8.2.2 2.c of the Servlet > specification and prevent a web application

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-17 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, Thanks for volunteering to RM this release. Sigs are correct. Unit test failure is environmental in nature. +1 to release STABLE 8.5.37 - -chris On 12/16/18 11:02, Christopher Schultz wrote: > All, > > On 12/12/18 08:22, Mark Thomas wrote:

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-17 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 12/17/18 11:37, Mark Thomas wrote: > On 17/12/2018 16:21, Christopher Schultz wrote: > > > >> 16-Dec-2018 11:01:04.189 INFO [main] >> org.apache.catalina.tribes.transport.ReceiverBase.bind Unable to >> bind server socket to:[/:4099]

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-17 Thread Mark Thomas
On 17/12/2018 16:21, Christopher Schultz wrote: > 16-Dec-2018 11:01:04.189 INFO [main] > org.apache.catalina.tribes.transport.ReceiverBase.bind Unable to bind > server socket to:[/:4099] throwing error. > 16-Dec-2018 11:01:04.190 SEVERE [main] >

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-17 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 12/17/18 05:49, Mark Thomas wrote: > On 16/12/2018 16:02, Christopher Schultz wrote: > > > >> I've got a signature problem with the Windows installer (see >> below). Everything else seems okay. I'll hold my +1 until we sort >> that out.

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-17 Thread Mark Thomas
On 16/12/2018 16:02, Christopher Schultz wrote: > I've got a signature problem with the Windows installer (see below). > Everything else seems okay. I'll hold my +1 until we sort that out. Ah. That is probably my fault. I managed to kill the release build after it had completed the Windows

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-16 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, On 12/12/18 08:22, Mark Thomas wrote: > The proposed Apache Tomcat 8.5.37 release is now available for > voting. > > The major changes compared to the 8.5.35 release are: > > - Implement the requirements of section 8.2.2 2.c of the Servlet

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-16 Thread Felix Schumacher
Am 12.12.18 um 14:22 schrieb Mark Thomas: The proposed Apache Tomcat 8.5.37 release is now available for voting. The major changes compared to the 8.5.35 release are: - Implement the requirements of section 8.2.2 2.c of the Servlet specification and prevent a web application from

Re: [VOTE] Release Apache Tomcat 8.5.37

2018-12-12 Thread Igal Sapir
On Wed, Dec 12, 2018 at 5:23 AM Mark Thomas wrote: > The proposed Apache Tomcat 8.5.37 release is now available for voting. > > The major changes compared to the 8.5.35 release are: > > - Implement the requirements of section 8.2.2 2.c of the Servlet > specification and prevent a web

[VOTE] Release Apache Tomcat 8.5.37

2018-12-12 Thread Mark Thomas
The proposed Apache Tomcat 8.5.37 release is now available for voting. The major changes compared to the 8.5.35 release are: - Implement the requirements of section 8.2.2 2.c of the Servlet specification and prevent a web application from deploying if it has fragments with duplicate names