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
Deliver saaj-api Specification Version update for Jakarta EE 9 #53
Comments
Can I ask this team to please create and assign the following labels to this Issue? Thank you! |
Hi @lukasj, I know you are busy with several fires at the moment... But, once we get an updated M1 or RC1 jar file for the SAAJ API, it would be great if we could advertise it via the Milestone/RC column on the Project Board. SAAJ is a Wave 1 deliverable. Thanks! |
I created this PR: #78
|
Looking for an update on the status of the SAAJ Final Specification PR. If we're going to make the Sept deliverable goal, then this Wave 1 Specification needs to be ready for final ballot by Monday, July 19. Which means that the Specification PRs should already be created and under a "mentorship" review. Can I ask what the plans are for this Specification? Thanks! |
@kwsutter I should be able to prepare spec PR for this today, even though my vacation has just started, but implementation won't be ready since it depends on ~5 other projects which needs to be finalized in specific order first (xml binding API being one of them) |
done |
Is your feature request related to a problem? Please describe.
Jakarta EE 9 is the next major release, with the main focus of moving from the
javax
namespace to thejakarta
namespace.Describe the solution you'd like
This issue will be used to track the progress of this work effort via the Jakarta EE 9 Project board.
Additional context
Jakarta EE Specification Process
Eclipse Project Handbook
Eclipse Release Record for Jakarta EE 9
ToDo
Most Component Release Records will just reference the Jakarta EE 9 Platform Release Plan. But, if your Component deviates at all from the Platform Release Plan, then a description of the changes will be required in the Release Record.
Again, if your component is only doing the required minimum as defined by the Jakarta EE 9 Platform Release Plan, then no separate ballot is required. You are already approved. But, if your component deviates from the Platform Release Plan, then you will need to initiate your own ballot as defined by the Jakarta EE Specification Process.
Many of the Jakarta EE components now have the source for their Specification documents. It is strongly recommended that these Specification documents are properly updated to represent Jakarta EE instead of Java EE. Some helpful instructions are documented here.
If your component has Specification source, then all javax package references need to be updated to use jakarta package references.
Your component APIs need to move from using the javax namespace to using the jakarta namespace.
A Release Candidate of your component API should be pushed to Maven Central as soon as humanly possible. This will allow other dependent components to utilize your APIs as they are updating their APIs. Multiple revisions of these Release Candidate APIs are allowed (and probably expected) during the development cycle.
Your component TCK needs to be updated to use the jakarta namespace.
Your compatible implementation that will be used to demonstrate completeness of the Specification needs to be updated to use the jakarta namespace.
When ready, your final version of the API needs to be staged to get ready for the PR review and approvals.
Like we did for Jakarta EE 8, draft PRs need to be created and reviewed in preparation for the final ballots.
Each Jakarta EE component will need to initiate a separate Release Review ballot after proper reviewing has completed. To be clear, there will not be a blanket Release Review for all of Jakarta EE 9 like we did for the Plan Review. Each component needs a separate Release Review.
The text was updated successfully, but these errors were encountered: