diff --git a/minutes/2024/2024-03-12.md b/minutes/2024/2024-03-12.md new file mode 100644 index 0000000..f3e99d6 --- /dev/null +++ b/minutes/2024/2024-03-12.md @@ -0,0 +1,241 @@ +# Jakarta EE Platform Call + +Date: 2024-03-12 + +Present: + +* Arjan Tijms (OmniFish) +* Ivar Grimstad (Eclipse Foundation) +* Petr Aubrecht (Payara) +* Jim Krueger (IBM) +* Jimmy Wu (IBM) +* Ed Burns (MSFT) +* Dmitry Kornilov (Oracle) +* Cesar Hernandez (Tomitribe) +* David Matějček (OmniFish) +* Brian Stansberry (Red Hat) +* Riva T Philip (IBM) + +## Agenda and Minutes + + +### [Jakarta EE 11 Release Plan](https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan) + +### First waves + +* Wave 1 - 4 release review initiated by 2024-02-29 (leap day) and M2 + * Ivar detailed “what happens next”. + * Emily suggested sharing the mentor assignment [spreadsheet](https://docs.google.com/spreadsheets/d/1YTUpfdLZZrk2_UGwoX2w0seOCueRO3sQJIjWxpDAa7g/edit#gid=1763049340). Select the **EE 11 Release Review** tab. + * Spec projects + * All seem ready to start their release review ballot this week + * **Jakarta Annotations 3.0*** + * [https://github.com/jakartaee/specifications/pull/699](https://github.com/jakartaee/specifications/pull/699) + * Staged: [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/annotation/jakarta.annotation-api/3.0.0/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/annotation/jakarta.annotation-api/3.0.0/) + * **BLOCKER**: GlassFish 8.0.0-M3 to be used for ratifying + * Will be released this week + * Ready to go, but needs the TCK results + * **Jakarta Expression Language 6.0*** + * [https://github.com/jakartaee/specifications/pull/701](https://github.com/jakartaee/specifications/pull/701) + * Staged: [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/el/jakarta.el-api/6.0.0/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/el/jakarta.el-api/6.0.0/) + * Needs TCK certification summary + * **BLOCKER**: Tomcat 11 M18 - seems to be in progress \ + + * **Jakarta Interceptors 2.2*** + * [https://github.com/jakartaee/specifications/pull/702](https://github.com/jakartaee/specifications/pull/702) + * Staged: [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/interceptor/jakarta.interceptor-api/2.2.0/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/interceptor/jakarta.interceptor-api/2.2.0/) + * No updates yet + * Depends on CDI for implementation + * Results also in CDI / Weld results \ + + * **Jakarta Contexts and Dependency Injection 4.1*** + * [https://github.com/jakartaee/specifications/pull/704](https://github.com/jakartaee/specifications/pull/704) + * Staged: + * [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/jakarta.enterprise.lang-model/4.1.0/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/jakarta.enterprise.lang-model/4.1.0/) + * [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/jakarta.enterprise.cdi-api/4.1.0/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/jakarta.enterprise.cdi-api/4.1.0/) + * [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/jakarta.enterprise.cdi-el-api/4.1.0/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/jakarta.enterprise.cdi-el-api/4.1.0/) + * Jakarta Lang Model 4.1 + * (Part of CDI) Scott Stark + * **Update**: Emily started ballot 13th March (CET) + * Service releases + * **Jakarta JSON Processing*** + * No change. 2.1.3 is out in Maven Central + * [https://repo1.maven.org/maven2/jakarta/json/jakarta.json-api/2.1.3/](https://repo1.maven.org/maven2/jakarta/json/jakarta.json-api/2.1.3/) + * **Jakarta Mai**l* + * Lukas + * Staged: [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/mail/jakarta.mail-api/2.1.3/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/mail/jakarta.mail-api/2.1.3/) + * Is now in maven central this week + * **Jakarta Activation*** + * Lukas + * Staged: [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/activation/jakarta.activation-api/2.1.3/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/activation/jakarta.activation-api/2.1.3/) + * Is now in maven central this week + * **XML Binding** + * Lukas + * Staging: [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/xml/bind/jakarta.xml.bind-api/4.0.2/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/xml/bind/jakarta.xml.bind-api/4.0.2/) + * **XMS WS** (wave 5) + * Staging: [https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/xml/ws/jakarta.xml.ws-api/4.0.2/](https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/xml/ws/jakarta.xml.ws-api/4.0.2/) + * Not in central yet + * 2024-02-29 and M2 actions + * Ed, Ivar, Arjan + * Outstanding spec text changes + * [https://github.com/jakartaee/platform/pull/807](https://github.com/jakartaee/platform/pull/807) + * Iterating on + * [https://github.com/jakartaee/platform/pull/855](https://github.com/jakartaee/platform/pull/855) + * Essentially done - due to be merged + * ACTION: review by Arjan + * Arjan: + * Interceptor’s spec should not be in the platform spec, but should be moved into the CDI spec. Functionally, it is CDI-like. + * Ed, this is a bigger deal. Probably not for 11. + * Injection of the **Principal** should be part of the security spec, instead of its current location, the CDI spec. Now moved to the platform spec in PR 855. + * Jared observed the Servlet aspect, and also points out that the Security spec TCK must test this assertion. + * [https://github.com/jakartaee/platform/issues/841#issuecomment-1962435660](https://github.com/jakartaee/platform/issues/841#issuecomment-1962435660) + * ACTION: Arjan to copy over Principal concerns to Security spec: + * [https://github.com/jakartaee/security/tree/master/spec/src/main/asciidoc](https://github.com/jakartaee/security/tree/master/spec/src/main/asciidoc) + * ACTION: Someone(?) remove + * Incorporation actions for updated XML Schemas + * M2 release + * Keep iterating 11.0.0-SNAPSHOT as artifacts come in after completing their release review then release 11.0.0-M2 from that. + * Policy of always updating, despite any normative changes being there or not + * Faces 4.1 - has an update with normative changes + +### Next waves +* Wave 5 release review initiated by 2024-03-29 + * Spec projects + * Jakarta Authorization* + * Arjan + * Emily sought a status. + * Arjan stated the most important part was done a while ago. TCK is part of the platform. RISK FACTOR. Arjan has a plan to mitigate this risk. + * “Two tck” solution. + * Policy class removal + * [JEA-345](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/345): Ed to capture this into the AzDO for resolution. + * Emily: will you plan to stage another milestone? + * Arjan: yes, targeting EE 11 M2 Authorization and Security. + * Authorization new TCK has started + * OLD (Javatest / Ant) based TCK still in platform + * Move that to an “old but standalone” TCK? + * Or keep and update within the platform? + * ACTION: Arjan sends mail to TCK list to ask + * Jakarta Persistence* + * Lukas + * Riva asked for the status for M2. [https://github.com/jakartaee/specifications/pull/703](https://github.com/jakartaee/specifications/pull/703) was filed and review was requested. + * M2 API in staging since Feb 29 + * Eclipselink 5 was staged a few days ago: [https://jakarta.oss.sonatype.org/content/repositories/staging/org/eclipse/persistence/eclipselink/5.0.0-B01/](https://jakarta.oss.sonatype.org/content/repositories/staging/org/eclipse/persistence/eclipselink/5.0.0-B01/) + * Which one will be used for compatible implementation?\ + * Dmitri said EclipseLink will be ready for the ballot next month + * Jakarta RESTful Web Services* + * Santiago + * 8 +1s for progress review of 4.0 + * Absolutely certainly going to pass + * RestEASY should be done by the end of the month + * Go for a minimal 4.0 + * Removing JAXB - primary driver + * Removing @ManagedBean annotation + * Small convenience feature + * Getting something from a header + * Needs a TCK test still + * ACTION: Dmitry communicate to team + * TCK updates + * [JEA-348](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/348): Jim Krueger to submit a PR to + + [https://github.com/jakartaee/specifications/blob/master/restful-ws/4.0/_index.md](https://github.com/jakartaee/specifications/blob/master/restful-ws/4.0/_index.md) in time for the spec committee to review next week 2024-03-06. + +1. Make a fork +2. Clone the fork locally +3. git remote add upstream [git@github.com](mailto:git@github.com):jakartaee/specifications.git +4. Make a branch +5. Check out the branch +6. Push to your fork +7. Issue a PR from your fork. + + + * [JEA-349](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/349): Ed to submit a PR to [https://github.com/jakartaee/platform/blob/gh-pages/jakartaee11/JakartaEE11ReleasePlan.md](https://github.com/jakartaee/platform/blob/gh-pages/jakartaee11/JakartaEE11ReleasePlan.md) For all occurrences of “version increment only” change to “service release” + * Jakarta Server Pages* + * Mark Thomas and Paul A. Nicolucci + * **M2** API was published to Maven Central last week + * Jakarta Servlet* + * Mark Thomas + * **M2** API was published to Maven Central last week + * Action: Arjan to ask about including CDI beans requirement + * Jakarta Validation* + * Scott Stark + * Waiting on dependencies to be staged, otherwise ready + * Jakarta WebSocket* + * Mark Thomas and Jan Supol + * Very close to final release + * Faces (re) discovered ordering issue between the two + * Discussion in Servlet: [https://github.com/jakartaee/servlet/issues/548](https://github.com/jakartaee/servlet/issues/548) + * Jakarta Tags (previously JSTL) merge into Jakarta Pages (previously JSP) + * Note: No need for a separate Tags anywhere anymore + * Busy work with doing service releases, reviews, etc + * Service release. No need to seek approval from the spec committee. + * Actions for 2024-03-29 and M3 + * Ed, Ivar, Arjan + * XML Schemas + * M3 release + * Outstanding spec text changes + * Jakarta EE 11 M2 release + * Final versions of specs in release review + * Wait until wave 1-4 released before pushing to Maven central + * Can stage now + * ACTION: Ivar to stage Jakarta EE 11 M2 +* Wave 6 + * Spec projects + * Jakarta Authentication* + * Arjan + * **Jakarta Concurrency*** + * Nathan Rauh + * Released(!): [https://repo1.maven.org/maven2/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-api/3.1.0-M2/](https://repo1.maven.org/maven2/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-api/3.1.0-M2/) + * [https://github.com/jakartaee/concurrency/issues/135](https://github.com/jakartaee/concurrency/issues/135) + * Jakarta Faces* + * Arjan + * Jakarta Standard Tag Library (dependency update). + * Paul Nicolucci + * Actions for 2024-04-27 and M4 release + * Ed, Ivar, Arjan + * XML Schemas + * M4 release + * Outstanding spec text changes +* Wave 7 + * Spec projects + * Jakarta Security* + * Arjan + * Jakarta Data* + * Nathan Rauh + * Actions: Pardon Ed’s ignorance, but exactly who needs to take actions to make this happen? + * Ed, Ivar, Arjan + * XML Schemas + * M5 release + * Outstanding spec text changes +* Wave 8 + * Platform Projects + * Jakarta Platform* (including appropriate content formerly in CDI EE) + * Jakarta Web Profile* (including appropriate content formerly in CDI EE) + * Jakarta Core Profile* + * Actions: + * Ed, Ivar, Arjan + * XML Schemas + * Final release + * Outstanding spec text changes + + +### Other business + +* Jakarta Data developments + * [JEA-336](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/336) + * [JEA-340](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/340). Ed to update release plan. Change “Wave 6, 7 specs release review initiated by 2024-04-27” to “Wave 6, 7 specs release review initiated by 2024-04-27. Exception for Data. Data will initiate release review by 2024-05-31.” +* Individual specification TCK requirements for specs getting major/minor updates in EE 11 + * [JEA-338](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/338) + * [https://github.com/jakartaee/jakarta.ee/issues/1868](https://github.com/jakartaee/jakarta.ee/issues/1868) +* EJBHome issue, raised by Jared Anderson. Platform TCK has to cover the platform requirements, and no more. For the EE 11 release, EJB will still be included. EJB includes 2.x interfaces. All optional components will be removed unless they are specifically included by the platform. Will the EE 11 platform include the requirement for EJB 2.1 to be implemented or not. + * If it is not, should we produce an EJB jar that does include them? An optional jar? + * There’s the TCK side + * There’s the platform side. +* Annotations TCK needed for GlassFish 8.0.0-M3 + * Is that [https://ci.eclipse.org/jakartaee-tck/job/11/job/standalone-tck/job/eftl-annotations-standalonetck-build/](https://ci.eclipse.org/jakartaee-tck/job/11/job/standalone-tck/job/eftl-annotations-standalonetck-build/) (???) + * Annotations doesn’t really its own TCK normally -> find out the what/how… +* Authorization new TCK has started + * OLD (Javatest / Ant) based TCK still in platform + * Move that to an “old but standalone” TCK? + * Or keep and update within the platform? +* Concurrency + * @Lock annotation + * Still time to add that? diff --git a/minutes/2024/2024-03-19.md b/minutes/2024/2024-03-19.md new file mode 100644 index 0000000..24af907 --- /dev/null +++ b/minutes/2024/2024-03-19.md @@ -0,0 +1,132 @@ +# Jakarta EE Platform Call + +Date: 2024-03-19 + +Present: + +* Ed Burns (Microsoft) +* Jared Anderson (IBM) +* Jim Krueger (IBM) +* Riva Philip (IBM) +* Nathan Rauh (IBM) +* Tom Watson (IBM) +* Jimmy Wu (IBM) +* James Perkins (Red Hat) +* Petr Aubrecht (Payara) +* Emily Jiang (IBM) +* Scott Marlow (Red Hat) +* Ed Bratt (Oracle) +* Dmitry Kornilov (Oracle) +* Arjan Tijms (OmniFish) +* John Clingan (Red Hat) +* Cesar Hernandez (Tomitribe) + +## Agenda and Minutes + +### Calendar business + +* Arjan, can you run next week, 2024-03-26? I have a schedule conflict. +* 2024-04-09 Cancel due to DevNexus and JavaLand + +### [Jakarta EE 11 Release Plan](https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan) + +### First waves + +* Wave 1 - 4 release review initiated by 2024-02-29 (leap day) and M2 + * Mentor assignment [spreadsheet](https://docs.google.com/spreadsheets/d/1YTUpfdLZZrk2_UGwoX2w0seOCueRO3sQJIjWxpDAa7g/edit#gid=1763049340). Select the **EE 11 Release Review** tab. + * Ballot status \ + +

>>>>> gd2md-html alert: inline image link here (to images/image3.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>

+ +![alt_text](images/image3.png "image_tooltip") + + * Milestone release status + * E/Arjan need to ensure the milestone release job is in good shape. + * Spec edit status + * XML Schema work + +### Next waves + +* Wave 5 release review initiated by 2024-03-29 + * [JEA-354](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/354) Ed to send email to the spec-project-leads about Wave 5 release review dates. + * Also Cc individual emails to spec project leads and dev lists + * Spec projects + * Jakarta Authorization* + * M2 API published to maven central + * Spec document needs to be updated + * Policy change types not a Java SE type, rather a Jakarta type. + * Assorted spec assertions. + * Authorization new TCK has started + * OLD (Javatest / Ant) based TCK still in platform + * This set of tests is small in number. Possible to move those over. + * Move that to an “old but standalone” TCK? + * Or keep and update within the platform? + * → Port tests (only 34) + * [https://repo1.maven.org/maven2/jakarta/authorization/jakarta.authorization-api/3.0.0-M2/](https://repo1.maven.org/maven2/jakarta/authorization/jakarta.authorization-api/3.0.0-M2/) + * [https://github.com/jakartaee/authorization/tree/master/tck](https://github.com/jakartaee/authorization/tree/master/tck) + * Jakarta Persistence* + * [JEA-355](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/356): Ed to send reminder to [jpa-dev@eclipse.org](mailto:jpa-dev@eclipse.org) mailing list + * M2 API published to maven central + * Jakarta RESTful Web Services* + * Small convenience feature + * Getting something from a header + * Needs a TCK test still + * Dmitry confirmed that Jersey will be a ratifying compatible implementation for EE 11, in addition to RESTEasy. + * TCK updates + * Progress review ballot has sufficient votes to pass. ACTION: Ivar to close today or tomorrow 2024-03-20. [https://www.eclipse.org/lists/jakarta.ee-spec/msg03204.html](https://www.eclipse.org/lists/jakarta.ee-spec/msg03204.html) + * Jakarta Server Pages* + * Mark Thomas and Paul A. Nicolucci + * **M2** API was published to Maven Central last week + * Jakarta Servlet* + * Mark Thomas + * **M2** API was published to Maven Central last week + * [DONE](https://www.eclipse.org/lists/servlet-dev/msg00638.html): Arjan to ask about including CDI beans requirement + * Jakarta Validation* + * Scott Stark + * Waiting on dependencies to be staged, otherwise ready + * Jakarta WebSocket* + * Tyrus 2.2.0 M1 has been released impl milestone + * [https://jakarta.oss.sonatype.org/content/repositories/staging/org/glassfish/tyrus/tyrus-bom/2.2.0-M1/](https://jakarta.oss.sonatype.org/content/repositories/staging/org/glassfish/tyrus/tyrus-bom/2.2.0-M1/) + * Mark Thomas and Jan Supol + * Very close to final release + * Faces (re) discovered ordering issue between the two + * Discussion in Servlet: [https://github.com/jakartaee/servlet/issues/548](https://github.com/jakartaee/servlet/issues/548) + * Service releases + * XML Web Services + * Jakarta Tags (previously JSTL) merge into Jakarta Pages (previously JSP) + * Note: No need for a separate Tags anywhere anymore + * Busy work with doing service releases, reviews, etc + * Service release. No need to seek approval from the spec committee. + * Actions for 2024-03-29 and M3 + * Ed, Ivar, Arjan + * XML Schemas + * M3 release + * Outstanding spec text changes + * Jakarta EE 11 M2 release + * Final versions of specs in release review + * Wait until wave 1-4 released before pushing to Maven central + * Can stage now + * ACTION: Ivar to stage Jakarta EE 11 M2 + * GlassFish 8 M3 incorporates most of those + * [https://github.com/eclipse-ee4j/glassfish/releases/tag/8.0.0-M3](https://github.com/eclipse-ee4j/glassfish/releases/tag/8.0.0-M3) +* Marlow: Can we have milestone releases for EE 11 Platform TCK artifacts? + * Any issue with milestone TCK releases using EFTL license? + * Can we release TCK Artifacts directly to a public Maven Repository? + * Can we push milestone releases of TCK Artifacts directly to a public Maven Repository? + + +### Other business + +* Jakarta Data + * Things did settle down, but people have been opening issues. + * Work is going on in the query language. + * [JEA-358](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/358): Ed to send mail to data-dev + * We discussed this in the platform project + * I understand there have been some changes committed that are not related directly to the JPQL subset. This is not what we agreed. Please cut it out. This slows down progress and jeopardizes the EE 11. +* Jakarta Transactions + * Module-info. Make the CDI dependency in the module-info static. If this is all that is done, it can be called a service release. + * If there are bigger changes, it will need to be a minor release. + * This is related to CDI. + * ACTION: Ed to ask Scott Stark to what extent this must be addressed for EE 11. + + diff --git a/minutes/2024/2024-03-26.md b/minutes/2024/2024-03-26.md new file mode 100644 index 0000000..f92a263 --- /dev/null +++ b/minutes/2024/2024-03-26.md @@ -0,0 +1,179 @@ +# Jakarta EE Platform Call + +Date: 2024-03-26 + +Present: + +* Jared Anderson (IBM) +* Emily Jiang (IBM) +* Jim Krueger (IBM) +* Riva Philip (IBM) +* Nathan Rauh (IBM) +* Tom Watson (IBM) +* Jimmy Wu (IBM) +* Ivar Grimstad (Eclipse Foundation) +* Arjan Tijms (OmniFish) +* Lukas Jungmann (Oracle) +* John Clingan (Red Hat) +* Majd Mostafavi (IJUG) +* Ed Bratt (Oracle) +* Dmitry Kornilov (Oracle) +* Kenji Kazumura (Fujitsu) +* Jan Westerkamp (iJUG) +* Cesar Hernandez (Tomitribe) + +## Agenda and Minutes + +### Calendar business + +* Arjan, can you run next week, 2024-03-26? I have a schedule conflict. +* 2024-04-09 Cancel due to DevNexus and JavaLand + * Removed from the Calendar (remember to sync if you have a copy) + +### [Jakarta EE 11 Release Plan](https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan) + +* **Jakarta Data** + * **JNoSQL in progress too** + * Creating a independent implementation by Red Hat + * But suitable for GlassFish??? + * Depends on “statelessEntityManager” + * EclipseLink might add it + * Time… + * Persistence 3.2 is priority + * Already issue for, but targeted for Jakarta EE 12/Persistence 4 + * [https://github.com/jakartaee/persistence/issues/374](https://github.com/jakartaee/persistence/issues/374) + * **[https://twitter.com/arjan_tijms/status/1771976557508333887](https://twitter.com/arjan_tijms/status/1771976557508333887)** + * **Can be add Hibernate as Jakarta Data implementation** + * **Hibernate 6.5.0.CR1 includes preview of Jakarta Data function** + * **On critical path for GlassFish** + * **Alternative servers for ratification?** + * **Open Liberty -> ???** + * **WildFly -> ???** + +### First waves + +* Wave 1 - 4 release review initiated by 2024-02-29 (leap day) and M2 \ + + * Mentor assignment [spreadsheet](https://docs.google.com/spreadsheets/d/1YTUpfdLZZrk2_UGwoX2w0seOCueRO3sQJIjWxpDAa7g/edit#gid=1763049340). Select the **EE 11 Release Review** tab. + * Ballot status \ + +

>>>>> gd2md-html alert: inline image link here (to images/image2.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>

+ +![alt_text](images/image2.png "image_tooltip") + + * Milestone release status + * E/Arjan need to ensure the milestone release job is in good shape. + * Spec edit status + * XML Schema work + * GlassFish M3 released for Jakarta Annotations + * Should not care about JDK 21/17 since only tests the jar for the signature + * Not starting GlassFish + * Lukas submitted Annotations results on both JDK 17 and JDK 21 + * ACTION: Ivar can start the ballot + +### Next waves + +* Wave 5 release review initiated by 2024-03-29 -> **3 DAYS FROM NOW!** + * [JEA-354](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/354) Ed send emails to the spec-project-leads about Wave 5 release review dates. + * Spec projects + * Jakarta Authorization* + * M2 API published to maven central + * Mentor: **Emily/Tom** + * Compatible Implementation available: + * Exousia [https://github.com/eclipse-ee4j/exousia](https://github.com/eclipse-ee4j/exousia) + * GlassFish [https://github.com/eclipse-ee4j/glassfish/tree/8.0](https://github.com/eclipse-ee4j/glassfish/tree/8.0) + * Spec document being updated now + * Policy change types not a Java SE type, rather a Jakarta type. + * Removal of SecurityManager + * Assorted spec assertions. + * Authorization new TCK has started + * Ported over small number of existing tests to Maven/Junit/Arquillian + * [https://github.com/jakartaee/authorization/tree/master/tck](https://github.com/jakartaee/authorization/tree/master/tck) + * Release TCK + * Atleast to the Eclipse download location + * Look into Maven central + * M3 release + * Jakarta Persistence* + * [JEA-355](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/356): Ed to send reminder to [jpa-dev@eclipse.org](mailto:jpa-dev@eclipse.org) mailing list + * M2 API published to maven central + * Mentor: **Ivar** + * 3.2.0 API now available in staging ←- final + * Spec document is available in spec PR ← final + * TCK and impl can be ready around end of next week + * 5th of April + * EclipseLink 5.0.0.Beta2 + * Hibernate 6.5.0.XXX + * Jakarta RESTful Web Services* + * Mentor: **Ivar** + * Dmitry confirmed that Jersey will be a ratifying compatible implementation for EE 11, in addition to RESTEasy. + * Flow into next week + * TCK updates + * Most everything in PRs, but very close + * [Ed Bratt] – Jakarta REST still has a couple of outstanding issues both in the Spec. and the TCK. It will not be done before the end of the week. Then, Jersey needs to pick up the final changes and achieve compatibility status. That won’t happen before next week (Week of Apr. 1) + * See this [Epic issue](https://github.com/jakartaee/rest/issues/1233) + * Also, this [Milestone](https://github.com/jakartaee/rest/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.0) + * Jakarta Server Pages* + * Mark Thomas and Paul A. Nicolucci + * Mentor: **Werner / Ivar** + * **M2** API was published to Maven Central last week + * No update for now, need to double check + * Jakarta Servlet* + * Mark Thomas + * Mentor: **Marcelo/Abraham** + * **M2** API was published to Maven Central last week + * [DONE](https://www.eclipse.org/lists/servlet-dev/msg00638.html): Arjan to ask about including CDI beans requirement + * Project lead Mark Thomas denies request (not enough time) + * Jetty committers continue to not understand the ask + * [**Lukas**] 6.1.0-M2 is not source compatible with the previous version + * New method added to interface + * Would need to update Grizzly + * Usage of default keyword needed + * No distinction between source / binary + * Jakarta Validation* + * Scott Stark + * Mentor: **Ivar** + * M2 API was published to Maven Central + * Waiting on dependencies to be staged, otherwise ready + * Hibernate Validation (EE 10 one) + * It just works already + * Jakarta WebSocket* + * Tyrus 2.2.0 M1 has been released impl milestone + * [https://jakarta.oss.sonatype.org/content/repositories/staging/org/glassfish/tyrus/tyrus-bom/2.2.0-M1/](https://jakarta.oss.sonatype.org/content/repositories/staging/org/glassfish/tyrus/tyrus-bom/2.2.0-M1/) + * Mark Thomas and Jan Supol + * Mentor: **Kenji** + * Very close to final release + * Faces (re) discovered ordering issue between the two + * Discussion in Servlet: [https://github.com/jakartaee/servlet/issues/548](https://github.com/jakartaee/servlet/issues/548) + * Service releases + * XML Web Services + * Jakarta Tags (previously JSTL) merge into Jakarta Pages (previously JSP) + * Note: No need for a separate Tags anywhere anymore + * Busy work with doing service releases, reviews, etc + * Service release. No need to seek approval from the spec committee. + * Actions for 2024-03-29 and M3 + * Ed, Ivar, Arjan + * XML Schemas + * M3 release + * Outstanding spec text changes + * Jakarta EE 11 M2 release + * Final versions of specs in release review + * Wait until wave 1-4 released before pushing to Maven central + * Can stage now + * Ivar will do that today + * ACTION: Ivar to stage Jakarta EE 11 M2 + * GlassFish 8 M3 incorporates most of those + * [https://github.com/eclipse-ee4j/glassfish/releases/tag/8.0.0-M3](https://github.com/eclipse-ee4j/glassfish/releases/tag/8.0.0-M3) +* Marlow: Can we have milestone releases for EE 11 Platform TCK artifacts? + * Any issue with milestone TCK releases using EFTL license? + * Can we release TCK Artifacts directly to a public Maven Repository? + * Can we push milestone releases of TCK Artifacts directly to a public Maven Repository? + + +### Other business + +* TCK updates for specs not updated, but needed to run on JDK 21 +* Dependency updates for specs not otherwise updated + * Connectors depends on Annotations 2.1.0, should be 3.0.0 + * [https://github.com/jakartaee/connectors/pull/146](https://github.com/jakartaee/connectors/pull/146) + + diff --git a/minutes/2024/2024-04-02.md b/minutes/2024/2024-04-02.md new file mode 100644 index 0000000..4213f15 --- /dev/null +++ b/minutes/2024/2024-04-02.md @@ -0,0 +1,148 @@ +# Jakarta EE Platform Call + +Date: 2024-04-02 + +Present: + +* James Perkins (Red Hat) +* Scott Marlow (Red Hat) +* Jared Anderson (IBM) +* Emily Jiang (IBM) +* Scott Kurz (IBM) +* Riva Philip (IBM) +* Nathan Rauh (IBM) +* Tom Watson (IBM) +* Jimmy Wu (IBM) +* Jim Krueger (IBM) +* Ed Burns (Microsoft) +* Ivar Grimstad (Eclipse Foundation) +* Nathan Erwin (Individual) +* Cesar Hernandez (Tomitribe) +* Jan Westerkamp (iJUG) +* Ed Bratt (Oracle) +* Arjan Tijms (OmniFish) +* Dmitry Kornilov (Oracle) +* Petr Aubrecht (Payara) + +## Agenda and Minutes + +### Calendar business + +* 2024-04-03 + * ACTION: send email: Ed is not able to attend the spec committee call tomorrow due to personal travel. +* 2024-04-09 Cancel due to DevNexus and JavaLand + * Removed from the Calendar (remember to sync if you have a copy) + * ACTION: Ed send email asking for people to meet up at DevNexus and JavaLand. + +### [Jakarta EE 11 Release Plan](https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan) + +### Top-of-mind from Ed and Arjan + +* Jakarta Data ratifying compatible implementation + * Replied to Gavin King: [https://twitter.com/edburns/status/1774810065561911428](https://twitter.com/edburns/status/1774810065561911428) + * This is still tied to Hibernate + * Arjan reiterates the request to move the code out to a separate project, a hacking project. + * This could be done with a throwaway SPI. + * Scott Marlow does observe that the **StatelessEntityManager**, while essential for Persistence.next itself, is not on the critical path for EE 11. + * Scott also observed this is not the appropriate forum. + * How is Liberty solving this problem? They use the **EntityManager** (stateful) as if it were stateless. Yes, it does pass the TCK. + * Dmitry did ask about the feasibility of IBM to make it possible for the Liberty data impl to serve as an extraction for the “hacking project”? + * Answers + * It is very deeply integrated into the rest of Liberty. + * It is not realistic from a human resource perspective. + * The impl itself is not in a state where it’s realistic to pull it out. + * While the impl is indeed open source, the impl is not in a good position to serve as an extraction for the “hacking project”. + * Emily did state that Liberty **will be the impl for passing the Data component spec **TCK but **IBM cannot commit to Liberty being the ratifying compatible implementation of the platform specification**. + + +### First waves + +* Wave 1 - 4 release review initiated by 2024-02-29 (leap day) and M2 \ + + * Mentor assignment [spreadsheet](https://docs.google.com/spreadsheets/d/1YTUpfdLZZrk2_UGwoX2w0seOCueRO3sQJIjWxpDAa7g/edit#gid=1763049340). Select the **EE 11 Release Review** tab. + * Ballot status \ + + +

>>>>> gd2md-html alert: inline image link here (to images/image1.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>

+ + +![alt_text](images/image1.png "image_tooltip") + + * Looks like Interceptors is having some trouble. + * How can we organize helping them resolve it? + * Ed Bratt stated that he would accept the presently mooted solution and change Oracle’s vote to +1. + * CDI: Emily stated that this will change to **DONE**. + * EL: Ivar changed it to **DONE**. + * Milestone release status + * Ed/Arjan need to ensure the milestone release job is in good shape: gpg key expired, needed to be updated. Currently. + * ACTION: Arjan to send an email to spec-project-leads reminding the responsible parties of the need to validate their gpg keys + * Subject: REMINDER: make sure your gpg keys for producing API artifacts from CI/CD jobs are refreshed. + * Spec edit status: ready for M2 spec release + * ACTION: Ed to make PR to update the page + * Make sure it clearly states **DRAFT** status and states **11.0.0-M2** as the version. + * XML Schema work: Not yet done. + + +### Current wave + +* Wave 5 release review initiated by 2024-03-29 + * Fully expect to have ballots started for all wave 5 specs this week or next. + * Spec projects + * Jakarta Authorization* + * PR + * Jakarta Persistence* + * PR + * Jakarta RESTful Web Services* + * PR in the next day or so + * Jakarta Pages* + * PR + * Jakarta Servlet* + * PR + * Jakarta Validation* + * PR + * Jakarta WebSocket* + * PR + * Service releases + * XML Web Services + * Jakarta Tags (previously JSTL) merge into Jakarta Pages (previously JSP) + * Actions for 2024-03-29 and M3 + * Ed, Ivar, Arjan + * XML Schemas + * M3 release + * Outstanding spec text changes + * Jakarta EE 11 M3 release + * Final versions of specs in release review + * Wait until wave 1-4 released before pushing to Maven central + * Can stage now + * GlassFish 8 M3 incorporates most of these Wave 5 specs + * [https://github.com/eclipse-ee4j/glassfish/releases/tag/8.0.0-M3](https://github.com/eclipse-ee4j/glassfish/releases/tag/8.0.0-M3) + + +### Next waves + +* Marlow: Can we have milestone releases for EE 11 Platform TCK artifacts? + * Any issue with milestone TCK releases using EFTL license? + * Yes, there is an issue. Milestone releases must not have the EFTL license. + * Can we release TCK Artifacts directly to a public Maven Repository? + * Yes. + * Can we push milestone releases of TCK Artifacts directly to a public Maven Repository? + * Yes. +* ACTION: Update release plan to change 2024-04-27 to 2024-04-26. +* Concurrency + * In RC2 + * This is what they intend to use for the 2024-04-26. + * Regarding the meaning of “virtual = true”? On 17: it is “ignore” +* Data + * Status update from Nathan + * Request for meeting between Ed and Nathan to be briefed on what is the absolute latest news on Data that you want to present during Ed and Ivar’s talks at JavaLand and DevNexus. + + +### Other business + +* Marlow: Not really a platform concern but still mentioning for sharing knowledge [https://github.com/jakartaee/specification-tools/blob/master/promotion/promote-release.sh](https://github.com/jakartaee/specification-tools/blob/master/promotion/promote-release.sh) doesn’t seem to add the EFTL license to TCK archives. + * Should it? + * No, because the promote script can not automatically add the EFTL license to the zip. + * Ed Bratt states this is because doing so would modify the SHA sum. Furthermore, if the contents of the zip file is changed, it would invalidate the CCRs based on proposed-final TCKs. +* Batch + * Question about spec update? in response to EE 10 TCK challenge [https://www.eclipse.org/lists/jakarta.ee-spec/msg03260.html](https://www.eclipse.org/lists/jakarta.ee-spec/msg03260.html) (which we’re waiting to resolve to release the TCK update supporting Java 21 for EE 11) + diff --git a/minutes/2024/2024-04-16.md b/minutes/2024/2024-04-16.md new file mode 100644 index 0000000..fa8da72 --- /dev/null +++ b/minutes/2024/2024-04-16.md @@ -0,0 +1,169 @@ +# Jakarta EE Platform Call + +Date: 2024-04-16 + +Present: + +* Ed Burns (Microsoft) +* Jared Anderson (IBM) +* Emily Jiang (IBM) +* Jim Krueger (IBM) +* Riva Philip (IBM) +* Nathan Rauh (IBM) +* Tom Watson (IBM) +* Jan Westerkamp (iJUG) +* John Clingan (Red Hat) +* Ivar Grimstad (Eclipse Foundation) +* Arjan Tijms (OmniFish) +* Jesse McConnell (Webtide) +* Dmitry Kornilov (Oracle) +* Scott Stark (Red Hat) +* Lukas Jungmann (Oracle) +* Kenji Kazumura (Fujitsu) + +## Agenda and Minutes + +### [Jakarta EE 11 Release Plan](https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan) + +### Top-of-mind from Ed and Arjan + +* DevNexus and JavaLand wrap ups + * Sessions + * JavaLand + * EE 11 update 150 people + * Hibernate 6 talk 239 people + * Jakarta EE CI/CD 60 people + * Jakarta EE applications talk 67 people + * Full day workshop on Spring Data JPA 26 people + * DevNexus + * Dedicated track, two full days. Ten talks total. + * Data talk was not that well attended. + * Track open: Ivar EE 11 update: Small room, more than half full. + * Track close: Michael Redlich EE 11 update. Small room, almost full. + * Emily and Brian talk was not that well attended. Around 15. Timing clashed with OpenRewrite AI talk. + * Discussion and suggestions: + * Tanja: Come up with snappier titles. Audiences are coming to look for 1. It’s going to be fully functional. 2. How to use it in apps. 3. People are regaining confidence in our technology. + * Strong desire for the working group to look into future development. If we do this right, we can get some of those numbers that Spring is getting at conferences like DevNexus. + * Arjan: 100% of people he talked to knew Spring. ~60% knew of Jakarta EE. + * Spring and AI was filled to overflowing. + * Exhibit presence + * JavaLand + * Need to get update from how it went with Carmen Delgado. + * Covered Adoptium, Jakarta EE, MicroProfile + * Customer feedback: customer requested EAP on 21. + * DevNexus + * IBM booth next to MicroProfile booth. + +### Any updates on the below from two weeks ago? \ + +* _“Jakarta Data ratifying compatible implementation_ + * _Scott Stark_ + * _Jakarta Data TCK: Hibernate based impl is having four falling tests, that make assertions about integration aspects._ + + +### First waves + +* Wave 1 - 4 release review initiated by 2024-02-29 (leap day) and M2 +* Jakarta EE M2 release + * PR: [https://github.com/jakartaee/specifications/pull/729](https://github.com/jakartaee/specifications/pull/729) + * Most Artifacts are in Maven Central + * Jakarta Interceptors 2.2 + * Ballot complete and approved + * In Maven central + * Jakarta Annotations 3.0.0 + * Ballot complete and approved + * In Maven central + * Jakarta Expression Language 6.0 + * Ballot complete and approved + * In Maven central + * Jakarta CDI 4.1 + * Ballot complete and approved + * In Maven central + * Specification artifacts + * [JEA-364](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/364) PR is ready for review and merging + * XML Schemas + * JEA-176 Schemas + + +### Current wave + +* Wave 5 release review initiated by 2024-03-29 + * Jared Anderson accurately observed that the release plan states “release review started” by 2024-03-29. This can be construed to include creating release review issue, mentor assignment, etc. + * Fully expect to have ballots started for all wave 5 specs this week or next. + * 16 April: only 2 ballots have started + * Spec projects + * Jakarta REST + * Ballot started, 5 +1’s + * Jakarta WebSocket* + * Ballot started, **Ballot withdrawn, Ballot will be restarted** + * SHA numbers did not match, so we will redo it. + * Jakarta Validation* + * PR,Mentor Spec Review Checklist, almost ready (1 tiny thing open) + * TCK user guide has a reference to “Bean Validation 3.0”? + * ACTION: Scott Stark is going to do a TCK re-release to address the GitHub issue raised by IBM (not a challenge). + * Jakarta Persistence* + * PR, Mentor Spec Review Checklist (11 things checked) + * Lukas asked to be able to use Hibernate as the ratifying compatible implementation together with EclipseLink. + * ACTION: Ivar to start the ballot by the end of the week. + * Jakarta Pages* + * PR, Mentor Spec Review Checklist (0 things checked) + * **ACTION**: Ivar to bring the mentorship matter up at Spec Committee tomorrow. + * Jakarta Servlet* + * **PR - tck missing in right location?** + * **ACTION**: Ivar to bring up the mentorship for this tomorrow. + * **ACTION**: Arjan will copy TCK to right location + * Jakarta Authorization* + * **PR - JDK 17 TCK run missing** + * ACTION: Spec review checklist can be added to the PR. [https://github.com/jakartaee/specifications/pull/721](https://github.com/jakartaee/specifications/pull/721) + * Ratifying compatible impl works on 17, but TCK includes an EJB test. So it does not run on Tomcat. + * ACTION: This is the matter that will finally force Arjan to create a special branch of GlassFish 8 that runs on JDK 17. + * Service releases + * XML Web Services + * Jakarta Tags (previously JSTL) merge into Jakarta Pages (previously JSP) + * Actions for 2024-03-29 and M3 + * Ed, Ivar, Arjan + * XML Schemas + * M3 release + * Outstanding spec text changes + * Jakarta EE 11 M3 release + * Final versions of specs in release review + * DONE: Wait until wave 1-4 released before pushing to Maven central + * Can stage now + * ACTION: Ivar to run job to push M3 to staging based on Arjan’s following statement: + * Arjan states that all of them are already in staging. + * GlassFish 8 M4 incorporates the Wave 5 specs + * [https://github.com/eclipse-ee4j/glassfish/releases/tag/8.0.0-M4](https://github.com/eclipse-ee4j/glassfish/releases/tag/8.0.0-M4) + + +### Next waves + +* Marlow: Can we have milestone releases for EE 11 Platform TCK artifacts? + * Any issue with milestone TCK releases using EFTL license? + * Yes, there is an issue. Milestone releases must not have the EFTL license. + * Can we release TCK Artifacts directly to a public Maven Repository? + * Yes. + * Can we push milestone releases of TCK Artifacts directly to a public Maven Repository? + * Yes. +* ACTION: Update release plan to change 2024-04-27 to 2024-04-26. +* Concurrency + * In RC2 + * This is what they intend to use for the 2024-04-26. + * Regarding the meaning of “virtual = true”? On 17: it is “ignore” +* Data + * Status update from Nathan + * Things are currently in a more settled down state + * April 19th target: finish the query language, TCK, impl is passing the TCK. + * ACTION: Ed to check in with Nathan on Monday 2024-04-22 to see his confidence level regarding the 2024-04-19 target. + + +### Other business + +* Marlow: Not really a platform concern but still mentioning for sharing knowledge [https://github.com/jakartaee/specification-tools/blob/master/promotion/promote-release.sh](https://github.com/jakartaee/specification-tools/blob/master/promotion/promote-release.sh) doesn’t seem to add the EFTL license to TCK archives. + * Should it? + * No, because the promote script can not automatically add the EFTL license to the zip. + * Ed Bratt states this is because doing so would modify the SHA sum. Furthermore, if the contents of the zip file is changed, it would invalidate the CCRs based on proposed-final TCKs. +* Batch + * Question about spec update? in response to EE 10 TCK challenge [https://www.eclipse.org/lists/jakarta.ee-spec/msg03260.html](https://www.eclipse.org/lists/jakarta.ee-spec/msg03260.html) (which we’re waiting to resolve to release the TCK update supporting Java 21 for EE 11) + + + diff --git a/minutes/minutes.md b/minutes/minutes.md index 0026c9d..0e86cfa 100644 --- a/minutes/minutes.md +++ b/minutes/minutes.md @@ -9,6 +9,11 @@ ## [2024](#2024) +* [2024-04-16](2024/2024-04-16.md) +* [2024-04-02](2024/2024-04-02.md) +* [2024-03-26](2024/2024-03-26.md) +* [2024-03-19](2024/2024-03-19.md) +* [2024-03-12](2024/2024-03-12.md) * [2024-03-05](2024/2024-03-05.md) * [2024-02-27](2024/2024-02-27.md) * [2024-02-20](2024/2024-02-20.md)