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
Jakarta Persistence 3.2 #714
Conversation
Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
✅ Deploy Preview for jakartaee-specifications ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
Mentor Spec Review Checklist
|
Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
CCR along with CI are pending, the rest is ready/completed |
EMO REVIEW CHECKLISTEDP Review status: COMPLETED EMO review checklistPMI record: https://projects.eclipse.org/projects/ee4j.jpa/reviews/3.2-release-review EF Specification Process
Intellectual Property Management
Open Source Rules of Engagement
General:
Things to check:
Branding and Trademarks
Things to check:
Legal Documentation
Recommended files:
See examples for Security file and Code of Conduct. Required elements:
Recommended elements:
Metadata (PMI)
|
added CCR, so I'm done here, I hope.. |
Everything looks great! Thanks @lukasj! |
Hibernate ORM is in the process of certifying. I don't think there are any spec changes/fixes necessary, but we found some problems in the TCK. There may be more, so we might create further PRs. I guess you need a final TCK version before publishing the spec as well? |
Are these changes to be considered as challenges to the TCK? Or are the changes of a kind that will invalidate the CCR for EclipseLink? |
Since we might request changes to the TCK, I would say that they "could" invalidate the CCR for EclipseLink. |
Yes, that is my question: Are the changes of a such nature that they are covered by the challenge process? |
Here are some further changes that improve the testing experience significantly: jakartaee/platform-tck#1291 |
my understanding is that as long as the ballot as such is not started, updates can be done without going through the challenge process and can be considered as dev-updates/regular bug fixes as long as the mentor and reviewer of this PR is fine with these changes and accepts a bit of additional work
from EL point of view, changes are OK, TCK was rebuilt, restaged, API and EL has been retested, CCR has been updated (see actual results) and everything was synced |
I do not consider this as important as the previous PR, but I'll leave it up to @ivargrimstad to say yes/no in this case. I have no problem with it from EL side and an argument to accept it now is that this particular change does not seem to fall under the challenge category, so it may be difficult to smuggle it in later as the challenge process does not allow this kind of changes |
It is entirely up to the Persistence project team. I am ready to start the ballot any time now, but when I do so, you can not make any more changes to the artifacts. Let me know if you want to make this change. Then I will hold off on starting the ballot until it is done. |
yes, we want. We also want to have Hibernate among ratifying implementations - what is the deadline for that? Can we afford waiting for that? |
The sooner, the better. Can you get it done by the beginning of next week? |
@beikov TCK has been refreshed, EclipseLink has been re-tested, CCR updated. Now it's your turn ;-) |
Thanks. We're working on it :) |
We are working on investigating a few remaining failures in our TCK run. We should be able to release a passing implementation and complete the certification request this week for sure; hopefully tomorrow - I am not in Europe :) |
Great! I will hold off starting the release review until Friday, or when you're done, whichever comes first |
@lukasj Hibernate has now filed a CCR. I have added the link in the PR comment. Can you add Hibernate to the list of Compatible implementations in the _index.md page? |
Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
@ivargrimstad added |
|
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://jakarta.oss.sonatype.org/content/repositories/jakartapersistence-1037/jakarta/persistence/jakarta.persistence-api/3.2.0/
https://www.eclipse.org/downloads/download.php?file=/ee4j/jakartaee-tck/jakartaee11/staged/eftl/jakarta-persistence-tck-3.2.0.zip
If desired, an optional second PR can be created to contain just the JavaDoc in the
apidocs
directory.Note: If any item does not apply, check it and mark N/A below it.