bin/boostrap_development already only works for Ubuntu 16.04+ because it's painful to get Java8 via apt-get on Ubuntu 14. The "profile=3" configuration in master already requires Java 8 at runtime, but will still compile with "java 7 source". Are you proposing to change https://github.com/cloudera/Impala/blob/2d2579cb31edda24457d33ff5176d79b7c0432c5/fe/pom.xml#L340 from 1.7 to 1.8?
I'm in favor of removing support for CentOS 5. Do we pay a tax for CentOS 6.8 vs older versions of CentOS 6? I worry there are more of those lying around than we care to admit. -- Philip On Fri, Jul 6, 2018 at 9:59 AM Sailesh Mukil <sail...@cloudera.com.invalid> wrote: > I'm in favor of the minimum OS version support proposal. From 3.x, I don't > see any reason to support much older OSes especially since it's becoming > much more burdensome to special case code for them and have those paths > tested. > > I'll defer to others on the minimum Java version proposal since they may > have better insight. > > On Fri, Jul 6, 2018 at 9:19 AM, Lars Volker <l...@cloudera.com.invalid> > wrote: > > > Hi All, > > > > With the automatic commit flow to the 2.x branch being disabled, I'd like > > to suggest that we deprecate support for some older operating systems on > > the 3.x branch. This would allow us to get rid of almost all the checks > in > > common/config.h.in as well as some workarounds in the code. It would > also > > simplify the upcoming rebase of the KRPC code (IMPALA-7006). > > > > I'd like to propose that we pick Ubuntu 14.04, CentOS 6.8, and SLES 12 as > > the minimum operating system versions on which Impala has to compile and > > pass all tests. I'd also like to deprecate support for Java 7 and require > > Java 8 for all changes going forward. To my knowledge these are the > minimum > > versions that people use for development and deployment of the 3.x > branch. > > > > I'm curious what others think. > > > > Cheers, Lars > > >
