You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Christopher Schultz <ch...@christopherschultz.net> on 2024/09/10 20:16:41 UTC

[VOTE][RESULT] Release Apache Tomcat 10.1.29

All,

The following votes were cast:

+1: markt, remm, rjung, dsoumis, schultz

No other votes were cast, therefore the vote passes.

Thanks to everyone who contributed toward this release.

-chris

> The proposed Apache Tomcat 10.1.29 release is now available for
> voting.
> 
> All committers and PMC members are kindly requested to provide a vote if possible. ANY TOMCAT USER MAY VOTE, though only PMC members votes are binding. We welcome non-committer votes or comments on release builds.
> 
> The notable changes compared to 10.1.28 are:
> 
> - If an HTTP/2 client resets a stream before the request body is fully
>   written, ensure that any ReadListener is notified via a call to
>   ReadListener.onErrror()
> 
> - An Exception being thrown during WebSocket message processing (e.g. in
>   a method annotated with @onMessage) should not automatically cause the
>   connection to close. The application should handle the exception and
>   make the decision whether or not to close the connection.
> 
> - Correct a regression in the fix for non-blocking reads of chunked
>   request bodies that caused <code>InputStream.available()</code> to
>   return a non-zero value when there was no data to read. In some
>   circumstances this could cause a blocking read to block waiting for
>   more data rather than return the data it had already received.
> 
> For full details, see the change log:
> https://nightlies.apache.org/tomcat/tomcat-10.1.x/docs/changelog.html
> 
> Applications that run on Tomcat 9 and earlier will not run on Tomcat 10 without changes. Java EE applications designed for Tomcat 9 and earlier may be placed in the $CATALINA_BASE/webapps-javaee directory and Tomcat will automatically convert them to Jakarta EE and copy them to the webapps directory.
> 
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-10/v10.1.29/
> 
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1513
> 
> The tag is:
> https://github.com/apache/tomcat/tree/10.1.29
> https://github.com/apache/tomcat/commit/6e9fc6759a00036f47e2c8f2dfa854109c6c600b
> 
> Please reply with a +1 for release or +0/-0/-1 with an explanation.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Re: [VOTE][RESULT] Release Apache Tomcat 10.1.29

Posted by Christopher Schultz <ch...@christopherschultz.net>.
All,

On 9/10/24 16:16, Christopher Schultz wrote:
> The following votes were cast:
> 
> +1: markt, remm, rjung, schultz

Oops technically dsoumis is non-binding.

Non-binding:
+1: dsoumis

> No other votes were cast, therefore the vote passes.
> 
> Thanks to everyone who contributed toward this release.

Thanks,
-chris

>> The proposed Apache Tomcat 10.1.29 release is now available for
>> voting.
>>
>> All committers and PMC members are kindly requested to provide a vote 
>> if possible. ANY TOMCAT USER MAY VOTE, though only PMC members votes 
>> are binding. We welcome non-committer votes or comments on release 
>> builds.
>>
>> The notable changes compared to 10.1.28 are:
>>
>> - If an HTTP/2 client resets a stream before the request body is fully
>>   written, ensure that any ReadListener is notified via a call to
>>   ReadListener.onErrror()
>>
>> - An Exception being thrown during WebSocket message processing (e.g. in
>>   a method annotated with @onMessage) should not automatically cause the
>>   connection to close. The application should handle the exception and
>>   make the decision whether or not to close the connection.
>>
>> - Correct a regression in the fix for non-blocking reads of chunked
>>   request bodies that caused <code>InputStream.available()</code> to
>>   return a non-zero value when there was no data to read. In some
>>   circumstances this could cause a blocking read to block waiting for
>>   more data rather than return the data it had already received.
>>
>> For full details, see the change log:
>> https://nightlies.apache.org/tomcat/tomcat-10.1.x/docs/changelog.html
>>
>> Applications that run on Tomcat 9 and earlier will not run on Tomcat 
>> 10 without changes. Java EE applications designed for Tomcat 9 and 
>> earlier may be placed in the $CATALINA_BASE/webapps-javaee directory 
>> and Tomcat will automatically convert them to Jakarta EE and copy them 
>> to the webapps directory.
>>
>> It can be obtained from:
>> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-10/v10.1.29/
>>
>> The Maven staging repo is:
>> https://repository.apache.org/content/repositories/orgapachetomcat-1513
>>
>> The tag is:
>> https://github.com/apache/tomcat/tree/10.1.29
>> https://github.com/apache/tomcat/commit/6e9fc6759a00036f47e2c8f2dfa854109c6c600b
>>
>> Please reply with a +1 for release or +0/-0/-1 with an explanation.
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org