> On Jul 20, 2025, at 11:04 AM, Richard Zowalla <r...@apache.org> wrote: > > Hi, > > Just a quick update: > > I created an API snapshot using JPA 3.2 and deployed it to repository.a.o. > Then, I updated the version on the jpa3.2 test branch and ran a full build, > including the TCKs where set up: > https://ci-builds.apache.org/job/Tomee/job/pull-request-manual/163/ > I also added a few tests to verify compatibility with EclipseLink, OpenJPA, > and Hibernate 6. > > Everything looks good so far. How shall we proceed? > > Maybe something like: > > (1) Release EE API with the fix for EL by Markus
Saw this thread come in and have been thinking and can't seem to find and good approaches. The concern is having something called Jakarta EE 10 API that has Jakarta EE 11 APIs in them. Ideally we call that out in some way a user could notice. I can't think of any good solutions other than to add some word to the version such as "modified" or "upgraded" or similar. Some kind of hint that could tip off a user. > > (2) Do a TomEE 10.1.x release with the fixes / dev upgrades we have so far We created a 10.1 because we changed the MicroProfile API level. I think that was a good call and we likely want to stay consistent with that practice and do a 10.2 to reflect the changed version, skipping 10.1. Are we upgrading our OpenJPA major version as well? > (3) Release EE API with JPA 3.2 + TomEE 10.2.x release soon after? This sounds like a good approach. -David
