On Tue, Jun 23, 2015 at 12:30 PM, Andrew Wang <andrew.w...@cloudera.com> wrote:
> There's no reason we have to choose 2.6 xor 2.7. If we have willing RMs and > enough PMCs who will vote on releases, there's no reason we can't maintain > both. > > However, based on the discussion at Hadoop Summit with Yahoo and Twitter, > their interest is primarily in 2.6, and Daryn mentioned the need to get 2.6 > stable before they can move to 2.7. So, if we want to help out these big > users, it seems like we should focus on maintaining 2.6. > > Allen also brought up the issue of JDK6. I see a few options (ranked best > to worst in my eyes): > > * Add multi-JDK support to test-patch > * Keep using JDK7 for precommit, and keep an eye on a nightly JDK6 run > * Drop support for JDK6 in 2.6.x, since no one is using it anymore > > #3 is the most easiest and probably fine for 95% of users, but doing a big > compat break is not how I'd want to kick off a stable release line. #2 > isn't too bad if we don't want to wait for #1. > > I believe work on adding multi jdk is on-going for patch test. Should be high on the list once we get our dev branch up. -- Sean
