Skip to main content

Jakarta EE Platform Project

Home for the Jakarta EE Platform Team

Jakarta EE Platform Call

Date: 2024-04-30

Present:

  • Jared Anderson (IBM)
  • Emily Jiang (IBM)
  • Jim Krueger (IBM)
  • Nathan Rauh (IBM)
  • Thomas Watson (IBM)
  • Adam Yoho (IBM)
  • James Perkins (Red Hat)
  • Petr Aubrecht (Payara)
  • Scott Marlow (Red Hat)
  • Jan Westerkamp (iJUG)
  • Ivar Grimstad (Eclipse Foundation)
  • Ed Burns (Microsoft)
  • Brian Stansberry (Red Hat)
  • Arjan Tijms (OmniFish)
  • Scott Stark (Red Hat)
  • Cesar Hernández (Tomitribe)
  • Werner Keil (Committer)

Agenda and Minutes

First waves

  • Wave 1 - 4 release review initiated by 2024-02-29 (leap day) and M2

Previous 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 complete and approved
        • Not yet in Maven central
      • Jakarta Validation*
        • Ballot is in progress. Ends on 01-05
        • 7 +1’s
      • Jakarta Authorization*
        • Ballot is in progress. Ends on 07-05
        • 6 +1’s
      • Jakarta Persistence*
        • Ballot technically ready to start
        • “Only” waiting for Hibernate. Hibernate has stated that they will be ready today, 2024-04-30.
        • Some TCK updates wanted by stakeholders
        • ACTION: Ivar to start the ballot when Hibernate gets or the end of the week, whichever comes first.
      • Jakarta WebSocket*
        • Ballot started, Ballot withdrawn, Ballot will be restarted
          • SHA numbers did not match, so we will redo it.
          • Needs Mark Thomas to address the outstanding issues are still not fixed.
          • ACTION: Ed to get involved on the GitHub PR and ask Mark how I can help. TCK must be re-run. I need to find out how to do this.
            • https://github.com/jakartaee/specifications/pull/713
      • Jakarta Pages*
      • Jakarta Servlet*
        • ACTION: Arjan to do the work to unblock this and seek sign-off from Mark Thomas.** **
        • PR - tck not in right format
          • TCK missing distribution version (userguide + artefacts in .zip)
          • Abondoned / forgotten? Last activity 28 days ago
          • ACTION: Ivar to bring up the mentorship for this tomorrow.
          • Action: Mark Thomas to address some issues.
          • https://github.com/jakartaee/specifications/pull/717
    • Service releases
    • Actions for 2024-03-29 and M3
    • Jakarta EE 11 M3 release
    • Before the ballot starts, you can make the necessary changes freely. Once a ballot starts, the code is frozen. If a change is needed, a ballot must be withdrawn. Once the change is done, a new ballot must be started with a new mentor review. If a SPEC API/TCK artifact has been released, any further changes will incur a release (see more info here).
    • When doing the platform TCK release, some TCK updates might happen on some component spec TCK outside platform TCK, which might require a new ballot.
    • Scott: Messaging, JSON-B, JSON-P (maybe more) TCKs are using EJB 2.x and they need to be updated.
    • Post EE 11

Current wave

  • Wave 6, 7 specs release review initiated by 2024-04-27
    • Spec projects
      • Jakarta Authentication*
        • ACTION: Arjan: file the PRs this week.
      • Jakarta Concurrency*
      • Jakarta Faces*
        • ACTION: Arjan: file the PRs this week.
      • Jakarta Security*
        • ACTION: Arjan: file the PRs this week.
      • Jakarta Data* (release review initiated by 2024-05-31)
        • The inflow of changes has ceased.
        • Working on TCK.
        • Nathan will remind team of the feature freeze at the next meeting.

          M4 release

    • XML Schemas JEA-176

Back to the top