| Re: [ee4j-pmc] Eclipse GlassFish release plan revision |
Dmitry, thanks for the update! :-) Questions: (1) Nov 5 Dependency Updates: Where is the *really final* official list of groupIDs to be used for that step? (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? Thanks -Markus From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Dmitry Kornilov Hi, In the light of the recent update from Eclipse Webmasters the GlassFish release plan needs adjustments. There are issues with fast provisioning of Jenkins instances (see attached email). The Eclipse plan assumes that the last Jenkins instance will be provisioned on Week 41 (ends 14 Oct 2018): https://docs.google.com/spreadsheets/d/1O2NA6YddYQy34riTabQd_lkNwwFzKq1HevxCJYNXrv4/edit#gid=0 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. Nov 30 -- Release Review completed. Comments? Thanks, Dmitry |