The transition has already been initiated, the specification page under the EE4J org is [here|https://projects.eclipse.org/projects/ee4j.jbv] (original proposal is [here|https://projects.eclipse.org/proposals/jakarta-bean-validation]).
Next steps:
* Track progress of [https://bugs.eclipse.org/bugs/show_bug.cgi?id=548104|https://bugs.eclipse.org/bugs/show_bug.cgi?id=548104], specifically we’re awaiting the creation of the repos for API/TCK/spec, they should show up at the [eclipse-ee4j|https://github.com/eclipse-ee4j] GitHub org eventually
* -Act on the “paperwork” mail send out by Eclipse-
* -Create card for BV at- [-https://github.com/orgs/eclipse-ee4j/projects/15-|https://github.com/orgs/eclipse-ee4j/projects/15] -(asked Ivar how to do that)- [It’s here|https://github.com/orgs/eclipse-ee4j/projects/15#card-23841477], cannot update it, though. It also lists the high-level steps needed.
* Move source code to the new repos and prepare the initial release, as described in [https://wiki.eclipse.org/How_to_Prepare_API_Projects_to_Jakarta_EE_8_Release|https://wiki.eclipse.org/How_to_Prepare_API_Projects_to_Jakarta_EE_8_Release] (e.g. replace mentions of “Java EE” with “Jakarta EE”); double-check with [initial contribution docs|https://www.eclipse.org/projects/handbook/#ip-initial-contribution] from the Eclipse handbook, e.g. AFAIU we must import only a single commit as the initial one, i.e. history will only be in the old repos unfortunately
* Set up a job for performing the release on the Eclipse CI project; this environment has been requested via [https://bugs.eclipse.org/bugs/show_bug.cgi?id=549158|https://bugs.eclipse.org/bugs/show_bug.cgi?id=549158]
* Do the initial release of API, spec and TCK
* Keep an eye on [https://www.eclipse.org/lists/jakartaee-spec-project-leads/|https://www.eclipse.org/lists/jakartaee-spec-project-leads/] and [https://accounts.eclipse.org/mailing-list/ee4j-pmc|https://accounts.eclipse.org/mailing-list/ee4j-pmc] for relevant infos
* Follow
Specific actions for the initial contribution process once we are happy with the packages spec repo : [https://www.eclipse.org/projects/handbook/#ip-initial-contribution|https://www.eclipse.org/projects/handbook/#ip-initial-contribution]
* Offer facilities for check version of the TCK to have the EFTL license in the final binary. see [https://docs.google.com/document/d/1Et3LtK tck - 2SUuAoOV56t8R8fKnRWhbWqg9SLgm-VhbDPY/edit?ts=5d27fb51#|https://docs audit . google.com/document/d/1Et3LtK-2SUuAoOV56t8R8fKnRWhbWqg9SLgm-VhbDPY/edit?ts=5d27fb51#|smart-link]
* Double check TCK needs and transform into actions [https xsl line 143 : //docs should we bump to 2 . google 0 . com/document/d/1Et3LtK-2SUuAoOV56t8R8fKnRWhbWqg9SLgm-VhbDPY/edit 1 ? ts=5d27fb51#|https://docs.google.com/document/d/1Et3LtK-2SUuAoOV56t8R8fKnRWhbWqg9SLgm-VhbDPY/edit?ts=5d27fb51#|smart-link]
Things needed clarification:
* Concern about RI and which artifact to depend on (please clarify, [~gsmet] )
* The “How to Prepare…” document mentions an Eclipse license for JavaDoc; that’s not quite clear to me how this should work
* TCK audit XML might need updating in case any assertions are affected by spec text changes
Other notes:
* The API and spec master branches contain a very small number of commits done after the 2.0.1 release. AFAICS, they are only about typo and other minor fixes. So I think it’s fair to release them as part of the transitioned artifact
|
|
