Community
Participate
Working Groups
We'll use this bug to track the release We require IP Team approval of the IP Log. We require PMC approval of the release and review materials. There's help regarding releases in the handbook. https://www.eclipse.org/projects/handbook/#release
The LICENSE and NOTICE file in jaf.git indicate that the license is a BSD-3-Clause variant. It appears that the EDL-1.0 was modified by replacing the copyright statement (I need to confirm with the IP Team, but I believe that this should not be modified). The license file for the TCK repo omits the EDL-1.0. All of the project content, including the specification document and API, was, AFAIK, contributed under the terms of the project licnese. AFAIK, the project is licensed as EPL-2.0 (with GPL 2.0+Classpath as secondary license) and EDL-1.0. Or, in SPDX, "EPL-2.0 OR BSD-3-Clause OR GPL-2.0 WITH Classpath-exception-2.0" Or I have I missed something important? The TCK repository is missing a CONTRIBUTING file.
The IP Log is approved.
Dmitry, has this been socialized with the specification committee? Do you believe that they are ready to start the ballot now?
ballot is about to end in a day or two, see: https://www.eclipse.org/lists/jakarta.ee-spec/msg00804.html
The EE4J PMC approves this release.
I've updated the release record for you, the date was still setup for July 15th. Since reviews run for at least a week and always conclude on the first and third Wednesdays of the month, I've scheduled this review to conclude on October 7th.
PMC approval: https://www.eclipse.org/lists/ee4j-pmc/msg02780.html
I declare this review successful. Please continue with your release.
