Hi, +1 for M1
Thank you Richard. On Mon 25 May 2026 at 19:49, Cesar Hernandez <[email protected]> wrote: > +1 for M1 > > On Fri, May 22, 2026 at 12:19 PM Markus Jung <[email protected]> wrote: > > > +1 for M1 release from me, we need to release the jakartaee-api artifact > > first for this. Should we also run a milestone for that one first as well > > or jump straight to 11.0.0? I should be able to run a release for the > > jakartaee-api in the coming days if everything looks good > > > > I think we should keep treating the Platform TCK coverage as optional for > > now, resource constraints still apply for that and its not too important > > for a milestone release IMHO > > > > > > Thanks > > > > Markus > > > > > On 22. May 2026, at 12:37, Richard Zowalla <[email protected]> wrote: > > > > > > Hi all, > > > > > > You can find the current EE11 status here: [1]. > > > > > > The only remaining item on our EE11 implementation list is OpenJPA > > (which doesn't implement a few other JPA 2.x and 3.x features anyway), > but > > it would work. > > > > > > The OPENJPA-2940 branch that passes the TCK hasn't been merged yet, but > > the OpenJPA folks are working on ironing out some niche quirks across the > > various DBMS out there. > > > > > > A few questions from my side: > > > > > > 1.) How do we want to proceed? What should we tackle next before going > > for a first TomEE 11 release? Should we aim for Platform TCK coverage? > > (Note: we didn't do this for TomEE 10.0.x or 10.1.x due to resource > > constraints.) > > > > > > 2.) Should we cut a milestone release to gather feedback, or go > straight > > to 11.0.0? ;-) Given our history, we could also do an M1 first (without > > OpenJPA JPA 3.2 support) and collect feedback that way. > > > > > > Happy to hear your thoughts and get a discussion going. > > > > > > Gruß > > > > > > Richard > > > > > > [1] https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-4530 > > > > > > > > -- > Atentamente: > César Hernández. >
