I agree. According to the spec committee each spec project will have a corresponding TCK project.
I do not want to break any rule. I want to propose that the the kit is split up. So the tests for JAX-RS are contained in *our* repo. We discussed this shortly earlier, and the JAX-RS committers do not see why we shall not keep the tests developed by US testing against OUR specification and interfaces, should be kept anywhere else than in OUR repo. We see that there are JAX-RS implementations that will never be part of a full Jakarte EE product, and those shall be able to get certified JAX-RS compliant. -Markus
thanks for the update! :-)
(1) Nov 5 Dependency Updates: Where is the *really final* official list of groupIDs to be used for that step? Good question. There was no official PMC voting for the groupId change. I tried to initiate it, but I didn’t see that it’s been finished. For me it’s still not clear, are we changing groupIds or not. I am asking other PMC members to make their votes.
(2) Oct 1 CTS: Spec projects correcting their spec / API might need to update "their" tests, as some tests are not precise enough. What is the plan? (A) All API committers become committers to the CTS project? (B) The CTS project is split up, i. e. e. g. JAX-RS tests removed from CTS repo / merged into JAX-RS repo? (C) API committers provide PRs against the common CTS? (D) Something else? The first release of GlassFish must be tested by Java EE (not Jakarta EE!) CTS/TCK binaries. Oct 1 milestone is mainly for Oracle to setup a job doing it. Moving CTS tests into project repositories or special TCK projects is the next step which will happen after the first Eclipse GlassFish release. According to EDP, any contributor can be elected as a committer after demonstrating some commitment (3 or more accepted PRs is usually enough). I think that now there are no reasons to break this rule.
According to the original GlassFish release plan all CI/CD related tasks must be finished before 1 Oct 2018. Assuming that there is some work needed after Jenkins instance provisioning (1 week), this date should be shifter forward for 3 weeks to Oct 22. Oct 22 is the first day of Oracle Code One. Suggested plan reflecting the situation is below. I marked bold all updated terms. The change doesn’t affect the GlassFish 5.1-RC1 milestone release, but it affects the final GlassFish 5.1 release. Sep 18 -- All code required for GF build contributed.
Sep 23 — Eclipse GlassFish builds.
Oct 1 -- Java EE 8 CTS testing. We are able to run CTS tests on Eclipse GlassFish.
Oct 22 — CI/CD release pipelines completed.
Oct 22 -- Eclipse GlassFish 5.1-RC1 milestone release.
Nov 5 — Dependencies updated. All projects are released to OSSRH and have dependencies to Eclipse version of other components. Nov 30 -- Release Review completed.
Dec 14 -- Eclipse GlassFish 5.1 release. All CTS tests are passed.
|
