forked from jakartaee/platform
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'upstream/gh-pages' into gh-pages
- Loading branch information
Showing
4 changed files
with
312 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,71 @@ | ||
| # Jakarta EE Platform Call | ||
|
|
||
| Date: 2024-01-30 | ||
|
|
||
| Present: | ||
|
|
||
| * Jan Westerkamp (iJUG) | ||
| * Arjan Tijms (OmniFish) | ||
| * James Perkins (Red Hat) | ||
| * Jim Krueger (IBM) | ||
| * Ed Burns (MSFT) | ||
| * Emily Jiang (IBM) | ||
| * Dmitry Kornilov (Oracle) | ||
| * Petr Aubrecht (Payara) | ||
| * Brian Stansberry (Red Hat) | ||
| * Tanja Obradovic (Eclipse Foundation) | ||
| * Scott Marlow (Red Hat) | ||
| * Riva T Philip (IBM) | ||
| * Majid Mostafavi (IranianJUG) | ||
| * Scott Stark (Red Hat) | ||
| * Ed Bratt (Oracle) | ||
| * Cesar Hernández (Tomitribe) | ||
| * John Clingan (Red Hat) | ||
|
|
||
| ## Agenda and Minutes | ||
|
|
||
| ### [JEA-276-mitigate-gh-platform-820](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/276) | ||
| * [JEA-289-request-progress-review-ballott](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/289) | ||
| * See [d537ee](https://github.com/azure-javaee/specifications/commit/d5357ee8b4345eec8edf5fcab7d8ed993cd6a4c9). | ||
| * Jan Westerkamp | ||
| * From an implementation perspective, we need to verify that 21 is also tested. | ||
| * There is a risk that component specs, because they have a choice to do 17 **or** 21**, instead of 17 and 21**, may have late-discovered problem when we do the platform testing toward the end of the release cycle. | ||
| * Ed proposed this remedy | ||
| * Stay on top of them to see if they can do the 17 and 21 testing. | ||
| * If a component spec is not able to do the non-mandatory **17 and 21** testing, offer help to do this testing. | ||
| * Emily yes, this is documented and agreed already. | ||
| * Tom Watson | ||
| * Again, this is identical to the 11/17 for EE 10 (now 17/21 for EE 11) | ||
| * Emily mentioned one possible interpretation of [https://www.eclipse.org/projects/efsp/?version=1.3](https://www.eclipse.org/projects/efsp/?version=1.3) compels us to produce a new milestone release. | ||
| * Ed observes that the process experts, Paul and Wayne, did not mention this. Therefore, Ed will proceed to comply with the existing request as shown in JEA-289 and cross this bring if we come to it. | ||
| * Brian Stansberry had a different reading about us being compelled. | ||
| * [Brian] This came from the more 'flexible' language in https://jakarta.ee/committees/specification/guide/#progress | ||
| * That language references the efsp language Emily linked, but otoh somewhat contradicts it (e.g. the projects "are not ready for a release yet"). Although 'milestone build' and 'release' are different terms, so I think Emily's interpretation is the better one. | ||
| * [JEA-279-GlassFish](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/279)-as-ratifying-compatible-implementation Jakarta Data help | ||
| * Confirm that Data can be reasonably implemented entirely based on existing primitives from Persistence and/or JDBC. | ||
| * See [discussion comment in the issue](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/279#4254914). Most important point: the need to get a “project” started to host collaboration for a Data impl that GlassFish can use. This is where the “chip in” work happens. | ||
|
|
||
| ### [JEA-275-EE11-M02](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/275) | ||
| * Date review | ||
| * [Jakarta EE 11 Release Plan](https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan) | ||
| * Risk factors | ||
| * REST 3.2 | ||
| * Progress being made is towards 3.2 that deprecates @Context injection, however Dmitry passed along a comment from Jan Supol that Jersey may not be able to find a clear way forward to allow Jersey to be a 3.2 impl. The stakeholders are engaged. | ||
| * Concurrency | ||
| * Issue open in the spec to change the API to | ||
| * Remove javadoc references, hard coding instead | ||
| * Some of that is held up about what is the 17 behavior when the user says virtual: true. | ||
| * ~~ACTION: Nathan, put a link to this issue. \ | ||
| Here is the issue where we could use more feedback in deciding the Java 17 behavior: \ | ||
| [https://github.com/jakartaee/concurrency/pull/415](https://github.com/jakartaee/concurrency/pull/415)~~ | ||
| * CDI | ||
| * Action to comply with the formerly known as CDI EE idea will also be taken in time for the 2024-02-29 release review. | ||
| * Jakarta Validation and Records status | ||
| * The M2 release is ready that has some aspects of this. The “new of a record” thing is obviously not possible to perform validation. | ||
| * They have what they plan to do for EE. For the most part, “records just work”. | ||
| * Jakarta Concurrency and Virtual Threads | ||
| * Overview of change to strategy vis a vis Java 17 | ||
| * Arjan: GlassFish will be doing a multi-release JAR to make this happen. Unclear how this will work in the server, it compiles, it runs the test, have not yet integrated in the server. | ||
|
|
||
| ### Beyond Jakarta EE 11 (if time allows) | ||
| * [Jakarta EE Working Group Brainstorm Document](https://docs.google.com/document/d/1tVaCmbXdAS_Ddn7LMPDelpOfAyozChXL/edit) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,109 @@ | ||
| # Jakarta EE Platform Call | ||
|
|
||
| Date: 2024-02-06 | ||
|
|
||
| Present: | ||
|
|
||
| * James Perkins (Red Hat) | ||
| * David Matějček (OmniFish) | ||
| * Ondro Mihalyi (OmniFish) | ||
| * Arjan Tijms (OmniFish) | ||
| * Jan Westerkamp (iJUG) | ||
| * John Clingan (Red Hat) | ||
| * Brian Stansberry (Red Hat) | ||
| * Jared Anderson (IBM) | ||
| * Jim Krueger (IBM) | ||
| * Riva Philip (IBM) | ||
| * Nathan Rauh (IBM) | ||
| * Tom Watson (IBM) | ||
| * Adam Yoho (IBM) | ||
| * Petr Aubrecht (Payara) | ||
| * Scott Marlow (Red Hat) | ||
| * Majid Mostafavi (IJUG) | ||
| * Ed Burns (MSFT) | ||
| * Dmitry Kornilov (Oracle) | ||
| * Nathan Erwin (Individual) | ||
| * Cesar Hernandez (Tomitribe) | ||
| * Emily Jiang (IBM, joined 38mins late) | ||
|
|
||
| Share comments suggestions to [https://purl.oclc.org/NET/edburns/contact](https://purl.oclc.org/NET/edburns/contact) | ||
|
|
||
| ## Agenda and Minutes | ||
|
|
||
| ### [JEA-276-mitigate-gh-platform-820](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/276) | ||
| * [JEA-294](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/294) track ballot | ||
| * Ivar will close the ballot at COB Wednesday 2024-02-07, after the world finishes with Tuesday 2024-02-06. | ||
| * [JEA-279](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/279)- Implementation help from Red Hat, or anyone else, for standalone Data impl to use in GlassFish and others: status? | ||
| * [Slack link](https://eclipsefoundationhq.slack.com/archives/CK4UW9DPS/p1706727503332949?thread_ts=1705429437.689559&cid=CK4UW9DPS) to appeal for help. | ||
| * [JEA-298-condition GLASSFISH_8_17_21](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/298) | ||
| * Big schedule risk: GlassFish committers started a vote in supporting JDK 17 / reverting. Unified opposition to go back to JDK 17. | ||
| * [https://github.com/eclipse-ee4j/glassfish/discussions/24790](https://github.com/eclipse-ee4j/glassfish/discussions/24790) | ||
|
|
||
| ### [JEA-275-EE11-M02](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/275) Date review | ||
| * [Jakarta EE 11 Release Plan](https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan) | ||
| * For release review, you need a TCK and a compatible implementation. | ||
| * Specs are welcome to go earlier than these dates, if desired. | ||
| * Wave 1, 2, 3, 4 specs release review initiated by 2024-02-29 | ||
| * Jakarta Annotations* | ||
| * Common annotations TCK still not in hand. Will hear more on the platform TCK call tomorrow. | ||
| * Jakarta JSON Processing* (service release) | ||
| * Jakarta Expression Language* | ||
| * Jakarta Interceptors* | ||
| * Jakarta Lang Model* | ||
| * Jakarta Activation* (service release) | ||
| * Jakarta Contexts and Dependency Injection* | ||
| * Jakarta Mail* (service release) | ||
| * Discussion notes | ||
| * Will the EE 10 TCKs for the service releases be refactored TCKs? | ||
| * ~~ACTION: Ed to respond to thread and share opinion that for component specs that only do a service release, we should not be using the refactored TCKs. Just stick with the same, non-refactored, ones for EE10.~~ | ||
| * After this, we will have M2. Other specs are encouraged to do a refresh of what they did for M1, with any updates. | ||
| * Wave 5 specs release review initiated by 2024-03-29 | ||
| * Jakarta Authorization* | ||
| * Has made significant progress, API is in good shape. | ||
| * TCK needs to be updated | ||
| * New tests within progress | ||
| * Existing tests within platform TCK | ||
| * Jakarta Persistence* | ||
| * EclipseLink status? Dmitry indicates it’s in good shape. | ||
| * Need to have a release for M2. | ||
| * Dmitry will pass to Lukas to get a release both for GlassFish and for EE11 M2. | ||
| * Jakarta RESTful Web Services* | ||
| * REST 3.2? | ||
| * ~~ACTION: Ed to request Santiago to join these platform calls.~~ | ||
| * Group has still not decided to pursue this 2024-03-29. | ||
| * Need to decide if we can use RestEasy instead of Jersey as the compatible implementation. | ||
| * Jan Supol is not sure if the proposals in 3.2 are implementable. Some of the matters are impl details. | ||
| 4. There are some outstanding questions, Dmitry requested other REST team members to follow up on Jan Supol’s questions. | ||
| * Jakarta Server Pages* | ||
| * Jakarta Servlet* | ||
| * Outstanding issues, but very likely not going to be addressed in EE 11 | ||
| * ServletContainerInitializer ordering. | ||
| * Jakarta Validation* | ||
| * Same as last week. | ||
| * Jakarta WebSocket* | ||
| * After this, we will have M3. Other specs are encouraged to do a refresh of what they did for M2, with any updates. | ||
| * Wave 6, 7 specs release review initiated by 2024-04-27 | ||
| * Jakarta Data* | ||
| * Jakarta Concurrency* | ||
| * Concurrency spec is now blocked on adding support for Java SE 17 because some participants are maintaining that the decision has not yet been made by the Platform to require support of Java SE 17. | ||
| * Nathan: some issues for 17 | ||
| * Waiting for the ballot to close. | ||
| * Participants are challenging the need to support it. | ||
| * ~~ACTION: put out an official statement on the support for 17.~~ | ||
| * Three options currently on the table: | ||
| 5. Virtual: true is simply treated as false if you are on 17. | ||
| 6. Virtual: true request will fail if running on 17. | ||
| 7. Behavior is left vendor specific. | ||
| * Jakarta Faces* | ||
| * Downgraded to 4.1, not a major release. Work done last December. Still need to pass the TCK. | ||
| * Jakarta Security* | ||
| * Builds on authorization, add the CDI native version of that work. Permission store concept. | ||
| * Emily observes the spec prose has not been updated. | ||
| * Arjan responds: the API and Javadoc is where the bulk of the normative assertions are made. | ||
| * Adam Yoho: No update on JWT in Security. It’s in the bridge spec. | ||
| * Jakarta Authentication* | ||
| * After this, we will have M4. Other specs are encouraged to do a refresh of what they did for M3, with any updates. | ||
| * Arjan: Multi-release JAR. Seeking reference to commit | ||
|
|
||
| ### Beyond Jakarta EE 11 (if time allows) | ||
| * [Jakarta EE Working Group Brainstorm Document](https://docs.google.com/document/d/1tVaCmbXdAS_Ddn7LMPDelpOfAyozChXL/edit) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,129 @@ | ||
| # Jakarta EE Platform Call | ||
|
|
||
| Date: 2024-02-13 | ||
|
|
||
| Present: | ||
|
|
||
| * John Clingan (Red Hat) | ||
| * Arjan Tijms (OmniFish) | ||
| * Jared Anderson (IBM) | ||
| * Emily Jiang (IBM) | ||
| * Jim Krueger (IBM) | ||
| * Riva Philip (IBM) | ||
| * Nathan Rauh (IBM) | ||
| * Adam Yoho (IBM) | ||
| * Tom Watson (IBM) | ||
| * Jimmy Wu (IBM) | ||
| * Jan Westerkamp (iJUG) | ||
| * Scott Marlow (Red Hat) | ||
| * Ed Bratt (Oracle) | ||
| * Dmitry Kornilov (Oracle) | ||
| * Lukas Jungmann (Oracle) | ||
| * Ed Burns (MSFT) | ||
| * Brian Stansberry (Red Hat) | ||
| * James Perkins (Red Hat) | ||
| * David Matějček (OmniFish, 15 minutes late) | ||
|
|
||
| ## Agenda and Minutes | ||
|
|
||
| ### [JEA-276-mitigate-gh-platform-820](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/276) | ||
| * [JEA-294](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/294) ballot completed. See summary at [platform-dev](https://www.eclipse.org/lists/jakartaee-platform-dev/msg04405.html). | ||
| * [JEA-279](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/279)- Implementation help from Red Hat, or anyone else, for standalone Data impl to use in GlassFish and others: status | ||
| * Ed Burns, Emily, Scott Stark met last week. | ||
| * JNoSQL as impl: See [JEA-301](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/301). | ||
| * Blocking concerns from Red Hat on Data spec | ||
| * [JEA-300](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/300) | ||
| * [JEA-298-condition GLASSFISH_8_17_21](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/298) | ||
| * Big schedule risk: GlassFish committers started a vote in supporting JDK 17 / reverting. Unified opposition to go back to JDK 17. | ||
| * [https://github.com/eclipse-ee4j/glassfish/discussions/24790](https://github.com/eclipse-ee4j/glassfish/discussions/24790) | ||
| * Twitter threads | ||
| * [https://twitter.com/dblevins/status/1755070093036560823](https://twitter.com/dblevins/status/1755070093036560823) | ||
| * [https://twitter.com/dblevins/status/1755368885535355140](https://twitter.com/dblevins/status/1755368885535355140) | ||
| * [https://twitter.com/OndroMih/status/1755364022159843695?s=20](https://twitter.com/OndroMih/status/1755364022159843695?s=20) | ||
| * Jakarta.ee-spec discussion: [https://www.eclipse.org/lists/jakarta.ee-spec/msg03191.html](https://www.eclipse.org/lists/jakarta.ee-spec/msg03191.html) | ||
|
|
||
| ### [JEA-275-EE11-M02](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/275) Date review | ||
| * [Jakarta EE 11 Release Plan](https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan) | ||
| * For release review, you need a TCK and a compatible implementation. | ||
| * Specs are welcome to go earlier than these dates, if desired. | ||
| * Wave 1, 2, 3, 4 specs release review initiated by 2024-02-29 (leap day) | ||
| * Jakarta Annotations* | ||
| * Common annotations TCK staged! Thanks! | ||
| * [https://jakarta.ee/committees/specification/tckprocess/](https://jakarta.ee/committees/specification/tckprocess/) needs an update still to allow Java SE TCKs to be used for Spec Ballot review. | ||
| * Is there a staged release of the Annotations 3.0 as well? | ||
| * Milestone 1 API has been released. | ||
| * CDI needs a final staging. | ||
| * Lukas just came back from vacation this week. | ||
| * Jakarta Expression Language* | ||
| * M2 API published in maven | ||
| * Alwin staged Standalone TCK at [https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee11/staged](https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee11/staged) (Tested with Glassfish8-M1, Tomcat - by spec team member). | ||
| * Also needs a TCK Process doc change to meet this date with a Java SE style TCK. | ||
| * Jakarta Interceptors* | ||
| * Scott will do a final release for interceptors. | ||
| * Jakarta Lang Model* | ||
| * Jakarta Contexts and Dependency Injection* | ||
| * Service releases | ||
| * Arjan: across-the-board dependency updates for service releases. | ||
| * Ed, Arjan, Ivar start making PRs to resolve these things now. | ||
| * Jakarta JSON Processing* | ||
| * Jakarta Activation* | ||
| * Jakarta Mail* | ||
| * Ed clarifies that these things must happen for M2. The M2 is scheduled to happen as soon as possible after the 2024-02-29 service releases. So, this work can happen after the 29th, but really should be as soon as possible. | ||
| * Discussion notes | ||
| * Will the EE 10 TCKs for the service releases be refactored TCKs? | ||
| * ~~ACTION: Ed to respond to thread and share opinion that for component specs that only do a service release, we should not be using the refactored TCKs. Just stick with the same, non-refactored, ones for EE10.~~ [JEA-313](https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/313) | ||
| * After this, we will have M2. Other specs are encouraged to do a refresh of what they did for M1, with any updates. | ||
| * Concurrency | ||
| * Security | ||
| * REST will not be releasing an artifact for M2. | ||
| * Emily observes this indicates risk for having an update to REST for EE 11. | ||
| * Wave 5 specs release review initiated by 2024-03-29 | ||
| * Jakarta RESTful Web Services* | ||
| * REST 3.2? | ||
| * ~~ACTION: Ed to request Santiago to join these platform calls.~~ Sent email. | ||
| * Group has still not decided to pursue this 2024-03-29. | ||
| * Need to decide if we can use RestEasy instead of Jersey as the compatible implementation. | ||
| * Jan Supol is not sure if the proposals in 3.2 are implementable. Some of the matters are impl details. | ||
| * There are some outstanding questions, Dmitry requested other REST team members to follow up on Jan Supol’s questions. | ||
| * Jakarta Authorization* | ||
| * Has made significant progress, API is in good shape. | ||
| * TCK needs to be updated | ||
| * New tests within progress | ||
| * Existing tests within platform TCK | ||
| * Jakarta Persistence* | ||
| * EclipseLink status? Dmitry indicates it’s in good shape. | ||
| * Need to have a release for M2. | ||
| * Dmitry will pass to Lukas to get a release both for GlassFish and for EE11 M2. | ||
| * Jakarta Server Pages* | ||
| * Jakarta Servlet* | ||
| * Outstanding issues, but very likely not going to be addressed in EE 11 | ||
| * ServletContainerInitializer ordering. | ||
| * Jakarta Validation* | ||
| * Same as last week. | ||
| * Jakarta WebSocket* | ||
| * After this, we will have M3. Other specs are encouraged to do a refresh of what they did for M2, with any updates. | ||
| * Wave 6, 7 specs release review initiated by 2024-04-27 | ||
| * Jakarta Data* | ||
| * Jakarta Concurrency* | ||
| * Concurrency spec is now blocked on adding support for Java SE 17 because some participants are maintaining that the decision has not yet been made by the Platform to require support of Java SE 17. | ||
| * Nathan: some issues for 17 | ||
| * Waiting for the ballot to close. | ||
| * Participants are challenging the need to support it. | ||
| * ~~ACTION: put out an official statement on the support for 17~~. See [email](https://www.eclipse.org/lists/cu-dev/msg00497.html). | ||
| * Three options currently on the table: | ||
| 1. Virtual: true is simply treated as false if you are on 17. | ||
| 2. Virtual: true request will fail if running on 17. | ||
| 3. Behavior is left vendor specific. | ||
| * Jakarta Faces* | ||
| * Downgraded to 4.1, not a major release. Work done last December. Still need to pass the TCK. | ||
| * Jakarta Security* | ||
| * Builds on authorization, add the CDI native version of that work. Permission store concept. | ||
| * Emily observes the spec prose has not been updated. | ||
| * Arjan responds: the API and Javadoc is where the bulk of the normative assertions are made. | ||
| * Adam Yoho: No update on JWT in Security. It’s in the bridge spec. | ||
| * Jakarta Authentication* | ||
| * After this, we will have M4. Other specs are encouraged to do a refresh of what they did for M3, with any updates. | ||
| * Arjan: Multi-release JAR. Seeking reference to commit | ||
|
|
||
| ### Beyond Jakarta EE 11 (if time allows) | ||
| * [Jakarta EE Working Group Brainstorm Document](https://docs.google.com/document/d/1tVaCmbXdAS_Ddn7LMPDelpOfAyozChXL/edit) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters