Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # dev >> Moving to JDK7, JDK8 and new major releases


Copy link to this message
-
Re: Moving to JDK7, JDK8 and new major releases
+1 (non-binding) for 2.5 to be the last release to ensure JDK6.

 >>> My higher-level goal though is to avoid going through this same pain
 >>> again when JDK7 goes EOL. I'd like to do a JDK8-based release
 >>> before then for this reason. This is why I suggested skipping an
 >>> intermediate 2.x+JDK7 release and leapfrogging to 3.0+JDK8.

I'm thinking skipping an intermediate release and leapfrogging to 3.0
makes it difficult to maintain branch-2. It's only about a half year
from 2.2 GA, so we should maintain branch-2 and create bug-fix releases
for long-term even if 3.0+JDK8 is released.

Thanks,
Akira

(2014/06/24 17:56), Steve Loughran wrote:
 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB