On Fri, Jan 11, 2019 at 8:29 PM Robert Varga <[email protected]> wrote: > On 11/01/2019 06:02, Michael Vorburger 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. > > > > > > +1 > > > > It seems reasonable to target Sodium to me. > > > > > > Speaking in an individual and personal capacity as upstream contributor > > and TSC member, I would support this. > > > > Perhaps conditional to just making sure that we actually can > > successfully build and run and CSIT say at least all mananged projects > > in autorelease on Java 11 at the start of Sodium? I would, of course, > > want to avoid a "broken world" - no surprise there to anyone with me > > saying this? ;-) > > > > Understood. > > Towards this, we really just need to have autorelease run with JDK11. > From infra perspective, we just need: > > - https://gerrit.linuxfoundation.org/infra/#/c/14105/ available in > releng/builder > - someone to create autorelease-jdk11 > - create JDK11 versions of CSIT jobs > > Then it's off to getting those jobs to pass, which should be pretty > straightforward after the current MRI bump patches. > > Any volunteers? > > Regards, > Robert >
Hello Robert: I've created a Jira RELENG-1648, for this "to create the AR/csit jobs with jdk11". I'll work on getting these jobs available on releng/builder. https://jira.linuxfoundation.org/browse/RELENG-1648 Thanks, Anil
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
