bq. We'll need to be strict after the switch: all patches to go into branch 2 
will have to go through yetus as branch-2 patches, then cherry picked to trunk, 
or a separate patch on the same JIRA done for the branch-2. Assuming yetus 
still tests the branch-2 stuff on JDK7, that will check version compatibility 
pre-commit.
+1. That's something I want to say also. We should have separate process for 
backport effort between Trunk and branch-2 then. Otherwise, we could involve 
Java 7 related bug to branch-2 after the backport.

Thanks,

Junping
________________________________________
From: Steve Loughran <[email protected]>
Sent: Wednesday, May 11, 2016 5:20 PM
To: Akira AJISAKA
Cc: [email protected]; [email protected]; 
[email protected]; [email protected]
Subject: Re: [DISCUSS] Set minimum version of Hadoop 3 to JDK8 (HADOOP-11858)

>
> On 10 May 2016, at 16:32, Akira AJISAKA <[email protected]> wrote:
>
> Hi developers,
>
> Before cutting 3.0.0-alpha RC, I'd like to drop JDK7 support in trunk.

+1

Given Robert Kanter first filed the patch to do this —why not give him the 
honour. In fact, why not have a webex screen share of the occasion so we can 
all celebrate?



> Given this is a critical change, I'm thinking we should get the consensus 
> first.
>
> One concern I think is, when the minimum version is set to JDK8, we need to 
> configure Jenkins to disable multi JDK test only in trunk.
>

LGTM

We'll need to be strict after the switch: all patches to go into branch 2 will 
have to go through yetus as branch-2 patches, then cherry picked to trunk, or a 
separate patch on the same JIRA done for the branch-2. Assuming yetus still 
tests the branch-2 stuff on JDK7, that will check version compatibility 
pre-commit
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to