​Having gone back through the entire thread I can see we've made progress here, as the discussion has moved on from when to move to java 7 to when to move to java 8... which, I've alway felt the appeal of from the coding-side. Java 8 tomorrow is the most compelling reason to move to java 7 today.
It also sets us up to thinking about java 9, where there are already early access releases available on java.net. But, as Colin McCabe <cmcc...@alumni.cmu.edu> wrote on 14 April 2014 09:22, > I think the bottom line here is that as long as our stable release > uses JDK6, there is going to be a very, very strong disincentive to > put any code which can't run on JDK6 into trunk. and there's a problem. I'm seeing push back now on flipping the java7 bit, I can imagine how a patch that went to java 8 and added some of the new streams operations would go down? Java 8 is radically different enough code-wise from java 6 that if you embrace those new features, you don't stand a chance of backporting. We need to move to a more recent java version in release hadoop, so that trunk & backported code can use java 7 code and libraries. Then trunk can flip the java 8 jvm bit -while still using java7 language- for as long as we plan to be able to move code/patches from trunk to release. This actually argues in favour of -renaming branch-2 branch-3 after a release -making trunk hadoop-4 -getting hadoop 3 released off the new branch-3 out in 2014, effectively being an iteration of branch-2 with updated java , moves of (off?) guava, off jetty, lib changes, but no other significant "big bang" features Hadoop 4.x then becomes the 2015 release, which can add more stuff. In particular, anything that goes into Hadoop 4 for which there's no intent to support in hadoop 2 & 3, can use the java 8 language features sooner rather than later. -Steve -- 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.
