Hello everyone, On 22/02/2019 00:28, Robert Varga wrote: > On 10/01/2019 19:30, Robert Varga wrote: >> As an alternative we could skip the combined Java 8/Java 11 release, >> going directly to a Java 11-only release -- either with Sodium or with >> Magnesium. >> >> I would like to start the discussion around the options we have and >> preferences of both OpenDaylight projects and our downstreams. > > Based on the feedback on this thread and the feedback I received from > users, it is clear that making a direct jump to Java 11 in Sodium would > be problematic to at least one of our open-source downstreams. > > In face of that, I propose we execute as follows: > > - have concurrent autorelease-openjdk8 and autorelease-openjdk11 builds > - do not have separate openjdk11 verify jobs > - stabilize autorelease-openjdk11 by the midway checkpoint > - Sodium release artifacts are still built with autorelease-openjdk8 > - evaluate feasibility of switching CSIT to Java 11 > > I am not sure about the last point -- we need to decide which JRE is > primary for Sodium. I would like to push for Java 11 being the primary, > and switching CSIT to it by midway checkpoint, but I am not sure if that > is feasible. > > Based on that, we would have: > > - Sodium compatible with Java 8 and Java 11, with recommended runtime > being either 8 or 11 (based on the CSIT question above).
the exact proposal lives here: https://lists.opendaylight.org/pipermail/tsc/2019-February/011134.html Proposed requirements on participation, as proposed there, have been adopted as Requirements for Participation in the Sodium Simultaneous Release on today's TSC call: https://meetings.opendaylight.org/opendaylight-meeting/2019/tsc/opendaylight-meeting-tsc.2019-03-07-17.00.html To re-iterate the requirements, they are only four points: > 1) Target Java platform remains Java 8. This means we build run > merge/autorelease jobs with Java 8. The artifacts that we produce as > Sodium will be built with Java 8. > > 2) All participating projects are required to built with JDK 11 no later > than the midway checkpoint. This requirement is checked by the > autorelease-sodium-openjdk11 job, which will remain in place for > duration of Sodium release. Current state is that the build fails on > ovsdb, but that is only a matter of removing tests (AI: me, already > agreed with OVSDB committers). > > 3) All participating project commit to support Java 11 as the run-time > environment and are required to run at least one sanity test with Java > 11 to ensure no obvious breakages are present by code freeze. > > 4) At the time of release both autorelease-openjdk8 and > autorelease-openjdk11 builds must be passing. Regards, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
