Mark,
On 8/12/24 14:30, Mark Thomas wrote:
All,
As I mentioned earlier, I am starting work on some new EL API features
that will be part of Jakarta EE 12 so implemented in Tomcat 12.
How do we want to handle this?
My current thinking is:
- create a 11.0.x branch from current main
- main becomes 12.0.x
I'm not expecting releases to start from 12.0.x any time soon. Users
that want to experiment with the new features can use snapshots. If we
reach a point where snapshots would be useful we can re-assess.
The other alternative I thought of was creating my own 12.0.x branch in
my fork but that seems wrong.
Yes, it means a little more back-porting but (for me at least) that is
all scripted and I'm not expecting many conflicts between 12.0.x and
11.0.x.
I'd update the CI systems to build 12.0.x.
Part of me thinks it is a little odd to be thinking about 12.0.x before
11.0.x is stable but on reflection I think it is a good thing that there
is momentum already for new features in Jakarta EE 12.
Oh, there is also a small change to the Servlet API we could pick up.
Thoughts?
Is there anything in Jakarta EE 12 that would actually be
_inappropriate_ for us to put into Tomcat 11?
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
