-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates to stage the core profile 11.0.0 release #782
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Scott M Stark <[email protected]>
✅ Deploy Preview for jakartaee-specifications ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
The 11.0.0 core proflie tck has been respun and this is the updated bundle info for the staged eftl binary:
The maven artifacts are also staged with repository ID jakartatck-1111.
|
Hi @starksm64, Here are the core profile specification documents (PDF and HTML) for you to add to the PR. |
Signed-off-by: Scott M Stark <[email protected]>
@ivargrimstad those have been added. It looks like the final apidocs are still needed. |
The API docs are in a separate PR. |
Ok, then should be good to go. |
@starksm64 the TCK is missing from the deployed view. Please see the Jakarta Core Profile 10.0 TCK (sig, sha, pub)) |
The software requirement was wrong:
|
The examples folder |
The TCK license is:
Just double checking that we do not require v 1.1 to be used at https://www.eclipse.org/legal/tck/. |
TCK reference guide section 3.2 has the wrong EE version
|
@starksm64 please address all of the above comments from me and @tjwatson |
Signed-off-by: Scott M Stark <[email protected]>
The remaining changes are going to require another respin of the coreprofile tck. |
Thanks @starksm64 |
Thanks @starksm64! Can you also list the two compatible implementations used for ratification (as is done for Core Profile 10)?
|
Signed-off-by: Scott M Stark <[email protected]>
I added the names, if we want the links to the downloads that will need to be added. |
By the way, after the core profile respin, the existing CCR from Open Liberty and Wildfly need to be redone. |
Has the TCK been updated again? They both have been respun once. |
Ah, I see it now. The updates to the user guide etc... I'll back the approved label from the CCRs so it Is reflected there |
The 11.0.0 core profile has been respun again and has been staged and uploaded to the project download area. The new info is:
The maven artifacts are also staged with repository ID jakartatck-1112.
|
This was updated to 1.1 since I had to update the TCK anyway |
Specification PR template
When creating a specification project release review, create PRs with the content defined as follows.
Include the following in the PR:
https://github.com/jakartaee/specification-committee/blob/master/spec_page_template.md
Instructions MAY be by reference.
https://www.eclipse.org/downloads/download.php?file=/ee4j/jakartaee-tck/jakartaee11/staged/eftl/jakarta-core-profile-tck-11.0.0.zip
*** SHA256SUM: 5722bac4f1af78e93ede95feaa448aa0bc19934d0871415c25dd45ffa8c5d1a5 ***
- Compatibility certification request for Open Liberty for Jakarta EE 11, Core Profile platform#975
- Compatibility certification request for WildFly Preview for Jakarta EE 11 Core Profile platform#978
Note: If any item does not apply, check it and mark N/A below it.
Below are for Jakarta EE Specification Committee
Mentor Spec Review Checklist
certification
label.If a Release Review is required, the specification project team contacts the EMO to initiate the review by sending an email to [email protected].
(A Release Review is not required if the current release is a Service Release based on a previously successful Major or Minor
release as indicated by a release record on the project's Releases page, e.g., the Jakarta Servlet releases page.)
Update Jakarta EE API jar
Mentor Final Tasks after a Successful Release Review
approved
label to the PRs, and sends out the Ballot Summary per this template to the public Jakarta EE Specification Committee email listusing the https://ci.eclipse.org/jakartaee-spec-committee/job/promote-release/ job. Manually editing the jenkins Build Information will help identify the build (ie. Mail 2.0 or CDI 3.0).
(an example can be found here.)