On Mon, Dec 12, 2022 at 11:22 AM David Delabassee
wrote:
>
> Welcome to the final OpenJDK Quality Outreach update for 2022!
>
> JDK 20, scheduled for General Availability on March 21 2023, is now in
> Rampdown Phase One (RDP1) [1]. At this point, the overall JDK 20 [2]
> feature set is frozen (see
Author: markt
Date: Tue Dec 13 14:40:05 2022
New Revision: 1905967
URL: http://svn.apache.org/viewvc?rev=1905967&view=rev
Log:
Add EOL notice for 8.5.x
Added:
tomcat/site/trunk/docs/tomcat-85-eol.html
tomcat/site/trunk/xdocs/tomcat-85-eol.xml
Modified:
tomcat/site/trunk/docs/whichvers
The Apache Tomcat team announces that support for Apache Tomcat 8.5.x
will end on 31 March 2024.
This means that after 31 March 2024:
- releases from the 8.5.x branch are highly unlikely
- bugs affecting only the 8.5.x branch will not be addressed
- security vulnerability reports will not be chec
Update with a corrected date for the anticipated final 8.5.x release.
The Apache Tomcat team announces that support for Apache Tomcat 8.5.x
will end on 31 March 2024.
This means that after 31 March 2024:
- releases from the 8.5.x branch are highly unlikely
- bugs affecting only the 8.5.x branch
On 12/8/22 20:35, Mark Thomas wrote:
Ping. Just a reminder we need one more PMC vote for this release.
[X] Stable - go ahead and release as 10.1.4
Tested of fedora36
Jean-Frederic
Thanks,
Mark
On 05/12/2022 17:42, Mark Thomas wrote:
The proposed Apache Tomcat 10.1.4 release is now av
All (mostly markt),
I'd like to volunteer to get ready to become the Tomcat 10.1 release
manager. My plan would be to start performing all of the necessary steps
except for anything which results in a public change (e.g. commits,
Maven pushes, etc.) in January with the expectation that I could
Sounds good to me.
I'm not sure there are many (any?) steps that don't result in a public
facing change. What sort of changes were you thinking of?
Mark
On 13/12/2022 18:05, Christopher Schultz wrote:
All (mostly markt),
I'd like to volunteer to get ready to become the Tomcat 10.1 release
https://bz.apache.org/bugzilla/show_bug.cgi?id=66388
Bug ID: 66388
Summary: Classpath resource having a name containing a space
can't be read anymore by
ClassLoader.getResources(String name)
Product: Tomcat 9
Vers
https://bz.apache.org/bugzilla/show_bug.cgi?id=66388
--- Comment #1 from sl...@aceslash.net ---
Just a quick word to add that this code change was also pushed to tomcat 10.1.3
and so it affect both the tomcat 9.0 and tomcat 10.1 branches.
--
You are receiving this mail because:
You are the assig
https://bz.apache.org/bugzilla/show_bug.cgi?id=66388
--- Comment #2 from Réda Housni Alaoui ---
Please note that the classloader involved in junit automatic tests (I suppose a
java native one) is able to retrieve the resource URI without any issue with
the space character:
> @Test
> void test()
10 matches
Mail list logo