On Fri, 11 Jan 2019, 11:52 Robert Varga <[email protected] wrote: > On 11/01/2019 06:02, Michael Vorburger wrote: > > I would like to start the discussion around the options we have > and > > preferences of both OpenDaylight projects and our downstreams. > > > > > > Speaking officially for Red Hat, we may need a week or so to internally > > discuss and confirm how this aligns with plans and time frames. My > > expectation is that it will be OK, but give us some time, and I will get > > back speaking for us and not just myself. > > Yes and I expect others and our downstreams (like fd.io, ONAP) will need > some time to consider this, too. > > If we are to do this in Sodium, the hard deadline is that the TSC must > make this part of the requirement to participate before Sodium release > starts -- i.e. at the TSC meeting of March 7th, 2019 at the very latest. > I have opened https://jira.opendaylight.org/browse/TSC-189 to track that > vote. >
As promised during our Kernel Projects weekly call on Tuesday, following an internal thread at Red Hat I can hereby state that there is no opposition from our side to going fully Java 11 for Sodium. -- If no other parties have strong objections and we actually go ahead and do do this, then to avoid a "broken world" we should obviously make sure that we actually can successfully build and run and CSIT say at least all managed projects in autorelease on Java 11 .... https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-neon-mvn35-openjdk11/ verifies that, and after some fixes (thanks Robert, Anil, Stephen, Lori...) is currently stuck in ovsdb due to https://jira.opendaylight.org/browse/OVSDB-476 ...
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
