Track progress of 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 GitHub org eventually
Act on the “paperwork” mail send out by Eclipse
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 (e.g. replace mentions of “Java EE” with “Jakarta EE”); double-check with initial contribution docs 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
Do the initial release of API, spec and TCK
Keep an eye on https://www.eclipse.org/lists/jakartaee-spec-project-leads/ and https://accounts.eclipse.org/mailing-list/ee4j-pmc for relevant infos
Specific actions for the spec repo:
check version of the tck-audit.xsl line 143: should we bump to 2.0.1?
check license of the tck-audit.xsl line 130 and consider changing it (me thinks no right now)?
Consider changing CONTRIBUTING.md to point to some eclipse email address instead? Update the website accordingly.
Update README.md to point to new repo for TCK tck-audit.xml file
Things needed clarification:
Concern about RI and which artifact to depend on (please clarify, )
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
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
Remove the references to JBoss repo in settings-example.xml
Evaluate dependencies we use and see if Eclipse cringes
Ask Eclispe which JDK 8 distro they use to test : it must have JavaFX
Could we ask an official question about whether we could keep the history?
Seems already asked Wayne about this (who is our mentor for BV at the EF), so let’s see what comes out of it.
We will also probably need to migrate the mailing lists (and all the references to them in TCK, API and documentation).
The relevant ones are: http://lists.jboss.org/pipermail/beanvalidation-dev/ and https://hibernate.atlassian.net/browse/BVTCK-210 .
Not sure if it should be done now (the one for the challenges is included in the TCK documentation)?