On October 21, 2016 at 1:29:37 PM, Joey Frazee (joey.fra...@icloud.com) wrote: Just submitted the PR for the pom enforcer updates for streams-master, streams and streams-examples and included a .java-version file for anyone using jenv. I can't do anything about the Jenkins jobs.
I merged the streams-master component, and that jenkins build is now failing. Looks like it might be connectivity (DNS) from builds to repo so let’s just see if it clears up. Once that step completes we’ll know the same mods on the other repos are fine to merge as well. In doing this also noticed that streams-examples isn't linked to JIRA. Can we do this or does this go to infra? This probably requires an infra ticket -joey On Oct 21, 2016, at 10:40 AM, Matt Franklin <m.ben.frank...@gmail.com> wrote: On Fri, Oct 21, 2016 at 11:24 AM sblackmon <sblack...@apache.org> wrote: So tactically: 1) switching all jenkins jobs to run latest jdk8 2) ensure all steps still pass 3) minor cleanup to code (if necessary) 4) changes to website documentation 5) perform release as usual using jdk8 I’ll make mention of this in the vote and announce language as well. Need to update poms also On October 21, 2016 at 10:11:12 AM, Matt Franklin ( m.ben.frank...@gmail.com) wrote: +1 On Fri, Oct 21, 2016 at 11:02 AM Suneel Marthi <suneel.mar...@gmail.com> wrote: > Seems like we have a consensus here, @Steve would u be taking care of this? > > On Fri, Oct 21, 2016 at 10:39 AM, Joey Frazee <joey.fra...@icloud.com> > wrote: > > > +1 > > > > On Oct 21, 2016, at 09:32 AM, sblackmon <sblack...@apache.org> wrote: > > > > +1. Impact should be minimal. > > > > Steve > > On October 21, 2016 at 9:29:49 AM, Suneel Marthi (smar...@apache.org) > > wrote: > > > > Proposing that we switch to Java 8 as of the upcoming release this > > weekend. > > Java 7 is EOL anyways. > > > > > > +1 from me. > > > > >
