| Hi All,
Just wanted to make sure we are all on the same page and reiterate our plan. We’ve decided (as reflected in our Roadmap) to work on two releases: 3.0 and 3.1. As I understand it, 3.0 will be proposed for Jakarta EE 9 in which case the process should be simpler as it is mostly a namespace rename.
Based on Kevin’s e-mail, we should start by creating a Release Record for 3.0 with reference to Jakarta EE 9. Please respond if you have any objections to move forward with this.
The complete set of steps from Kevin’s e-mail are shown below.
— Santiago
- Create Eclipse Release Record in your respective Jakarta Specification Project.
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. - Initiate a ballot for your Jakarta Release Record/Plan.
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. - Jakarta-ize your Specification document (if applicable)
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. - javax -> jakarta Spec updates
If your component has Specification source, then all javax package references need to be updated to use jakarta package references. - javax -> jakarta API updates
Your component APIs need to move from using the javax namespace to using the jakarta namespace. - Release Candidate (RC) of Jakarta API in Maven Central
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. - javax -> jakarta TCK updates
Your component TCK needs to be updated to use the jakarta namespace. - javax -> jakarta Compatible Implementation updates
Your compatible implementation that will be used to demonstrate completeness of the Specification needs to be updated to use the jakarta namespace. - Final Jakarta API available in Staging Repo
When ready, your final version of the API needs to be staged to get ready for the PR review and approvals. - Draft Specification and Apidoc PRs ready for review
Like we did for Jakarta EE 8, draft PRs need to be created and reviewed in preparation for the final ballots. - Release Review Ballot started
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.
|
