The proposed Apache Tomcat 8.0.0 release candidate 4 is now available
for voting.
Given this is a release candidate I am working on the basis that it is
equivalent to an alpha. The main changes since RC3 are:
- Stability fixes in the APR/native connector
- Stability fixes for non-blocking IO and W
On Oct 15, 2013, at 8:48 AM, Mark Thomas wrote:
> The proposed Apache Tomcat 8.0.0 release candidate 4 is now available
> for voting.
>
> Given this is a release candidate I am working on the basis that it is
> equivalent to an alpha. The main changes since RC3 are:
> - Stability fixes in the AP
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Tuesday, October 15, 2013 2:49 PM
> To: Tomcat Developers List
> Subject: [VOTE] Release Apache Tomcat 8.0.0-RC4
>
> The proposed Apache Tomcat 8.0.0 release candidate 4 is now available
>
[X] Alpha - go ahead and release as 8.0.0-RC4 alpha
Focused on websocket testing, default configuration.
-- Jeanfrancois
On 2013-10-15 8:48 AM, Mark Thomas wrote:
The proposed Apache Tomcat 8.0.0 release candidate 4 is now available
for voting.
Given this is a release candidate I am working
On 15/10/2013 17:31, Konstantin Preißer wrote:
> Note, that the documentation index.html included in the binaries
> says:
>
> "Apache Tomcat version @VERSION_MAJOR_MINOR@ implements the Servlet
> 3.1 and JavaServer Pages 2.3 specifications from the Java Community
> Process [...]"
>
> I guess thi
On 15/10/2013 15:23, Daniel Mikusa wrote:
> Tested a couple apps that I have and everything worked OK for me.
> One note though, there are some errors with the examples when I run
> with the security manager enabled.
>
> Here are the steps to replicate the issues:
>
> 1.) Downloaded Tomcat 8.0.0-
Because of the easily triggered JVM crash when using APR, SSL and
upgraded connections (e.g. via WebSocket) I am cancelling this release vote.
I did think about letting this vote run but a known JVM crash seemed too
serious to allow the vote to continue and it isn't as if rolling a new
RC is a gre
