[tomcat] branch 10.1.x updated: This file is managed in the main branch

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch 10.1.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/10.1.x by this push:
     new c75defb071 This file is managed in the main branch
c75defb071 is described below

commit c75defb071e345063e78f2ee29ed762c9c211e0d
Author: Mark Thomas <ma...@apache.org>
AuthorDate: Tue Oct 11 19:29:38 2022 +0100

    This file is managed in the main branch
---
 TOMCAT-NEXT.txt | 34 ----------------------------------
 1 file changed, 34 deletions(-)

diff --git a/TOMCAT-NEXT.txt b/TOMCAT-NEXT.txt
deleted file mode 100644
index 3cf744e81b..0000000000
--- a/TOMCAT-NEXT.txt
+++ /dev/null
@@ -1,34 +0,0 @@
-================================================================================
-  Licensed to the Apache Software Foundation (ASF) under one or more
-  contributor license agreements.  See the NOTICE file distributed with
-  this work for additional information regarding copyright ownership.
-  The ASF licenses this file to You under the Apache License, Version 2.0
-  (the "License"); you may not use this file except in compliance with
-  the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing, software
-  distributed under the License is distributed on an "AS IS" BASIS,
-  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-  See the License for the specific language governing permissions and
-  limitations under the License.
-================================================================================
-
-Notes of things to consider for the next major Tomcat release (11.x)
-
- 1. Implement OCSP checks for client certs with NIO/NIO2.
-    Useful reference:
-    https://stackoverflow.com/questions/5161504/ocsp-revocation-on-client-certificate
-
- 2. Integrate Panama OpenSSL module once Java 21 is available. Building Tomcat
-    releases would then require at least Java 21.
-
- 3. Add QUIC support using OpenSSL and Panama.
- 
- 4. Remove SecurityManager (assuming Jakarta EE 11 does so).
- 
- 5. Update minimum Java version to 17 (assuming Jakarta EE 11 does so).
- 
- 6. Implement an optional Loom module that provides
-    o.a.c.http11.Http11BioLoomProtocol


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