If there are not a lot of changes just to make Java 7 a requirement (I understand it's basically pom changes and unit test failure and findbugs fallouts), how about merging that with the next release and declare the next release and on Java-7-only?
On Mon, Dec 8, 2014 at 3:02 PM, Steve Loughran <ste...@hortonworks.com> wrote: > On 8 December 2014 at 19:48, Colin McCabe <cmcc...@alumni.cmu.edu> wrote: > > > Are there a lot of open JDK7 > > issues that would require a release to straighten out? > > > > I don't think so --the 2.6 release was tested pretty aggressively on JDK7, > and solely on it for Windows. Pushing out a 2.7 release would be more > symbolic than of use to people > > there's one exception: the fix for java 8 security. I do also think there > may be Java 8 test failures; these need to be identified and fixed ... > which would point more to a 2.8 release for that > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
