Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
From: Junping Du <jdu@hortonworks.com>
To: Arun Suresh <asuresh@apache.org>, =?iso-2022-jp?B?GyRCPVNKP0VIGyhC?=
	<dujunping@gmail.com>, Vinod Vavilapalli <vinodkv@hortonworks.com>
CC: "subru@apache.org" <subru@apache.org>, "common-dev@hadoop.apache.org"
	<common-dev@hadoop.apache.org>, "yarn-dev@hadoop.apache.org"
	<yarn-dev@hadoop.apache.org>, "hdfs-dev@hadoop.apache.org"
	<hdfs-dev@hadoop.apache.org>, "mapreduce-dev@hadoop.apache.org"
	<mapreduce-dev@hadoop.apache.org>
Subject: Re: Cutting branch-2.9
Thread-Topic: Cutting branch-2.9
Thread-Index: AQHTUbbYNd5/BaW4O0mirTpe/faCBKL+4/KAgAAOWICAAC8eAIADkeWAgACdJfw=
Date: Fri, 3 Nov 2017 23:24:42 +0000
Message-ID: <1509751548995.25843@hortonworks.com>
References: <CAOScs9b+WmQu9+EU3o3xYVeLt3cz-OM6WWMbRwxuYJJFJMBooA@mail.gmail.com>
 <CAGCyb54ojWTC+GbhPwrTvztZG3bmEJ6omzrsTu69vKJT1pvbPQ@mail.gmail.com>
 <CADaA6Ktt9jAsib355TPUJBJUvskN4oGdu4iRfcxyD5U_Okbw4g@mail.gmail.com>
 <CAGCyb54zs5JSGUVPCZySFKDSD+=pMcHatyid2qA07bBRboPK3g@mail.gmail.com>,<CAGCyb55ruzMc=U4byYwSwRmNnd16DbmTd=J41tjD2=zBd=TfQA@mail.gmail.com>
In-Reply-To: <CAGCyb55ruzMc=U4byYwSwRmNnd16DbmTd=J41tjD2=zBd=TfQA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 03 Nov 2017 23:24:59 -0000

Below is some findings from my recently run of JACC (https://builds.apache.=
org/job/Hadoop-2.9-JACC/12/artifact/target/compat-check/report.html) job ag=
ainst 2.9 and 2.8.2. I have discussed with Arun and Subru offline on jdiff =
report who convinced me some of items are not a big concern. Just tried to =
list here in case people in community have different voices:=0A=0A My origi=
nal concerns of incompatibilities:=0A     1. It looks like we change from l=
og4j to sel4j (HADOOP-12956) in 2.9 which is a huge incompatible change. Do=
 we have consensus on this in community - as I saw HBase community are deny=
 this kind of change in minor release? I talked with several other guys who=
 seems to have different opinion.=0A=0A    2. Some APIs (deprecated in 2.8)=
 get removed. My understanding is we only remove deprecated API in next maj=
or release (3.0) but not minor release. - Arun and Subru convinced me that =
removed 2 methods are not supposed to be used by other downstream projects=
=0A=0A    3. Some stable APIs get removed, like: YarnScheduler.allocate(), =
etc. We may need to add it back for compatibility of Scheduler API.=0A=0ATh=
oughts?=0A=0AThanks,=0A=0AJunping=0A=0A____________________________________=
____=0AFrom: Arun Suresh <asuresh@apache.org>=0ASent: Thursday, November 2,=
 2017 11:55 PM=0ATo: =1B$B=3DSJ?EH=1B(B=0ACc: Arun Suresh; subru@apache.org=
; common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop=
.apache.org; mapreduce-dev@hadoop.apache.org=0ASubject: Re: Cutting branch-=
2.9=0A=0AQuick update folks.=0A=0AWe just cut branch-2.9.0, and set the mvn=
 version to 2.9.0=0AWe've also updated the version on branch-2.9 to 2.9.1-S=
NAPSHOT.=0A=0AExpect an RC in the next 24 hrs :)=0A=0ACheers=0A-Arun/Subru=
=0A=0AOn Tue, Oct 31, 2017 at 5:24 PM, Arun Suresh <arun.suresh@gmail.com> =
wrote:=0A=0A> Hi Junping,=0A>=0A> > In the mean time, branch-2.9 should be =
reserved for next 2.9 point=0A> release (2.9.1) and branch-2 should be rese=
rved for next minor release=0A> (2.10.0 or whatever name it is). Thoughts?=
=0A> Yup, That is the current plan. We've updated mvn versions in branch-2 =
to=0A> point to 2.10.0-SNAPSHOT.=0A> Once we cut branch-2.9.0, we will upda=
te mvn versions on branch-2.9.0 to=0A> 2.9.0 and set versions on branch-2.9=
 to 2.9.1-SNAPSHOT (We plan to do that=0A> by Thursday)=0A>=0A> Cheers=0A> =
-Arun=0A>=0A> On Tue, Oct 31, 2017 at 2:35 PM, =1B$B=3DSJ?EH=1B(B <dujunpin=
g@gmail.com> wrote:=0A>=0A>> Hi Arun/Subru,=0A>>     Thanks for updating on=
 2.9.0 release progress. A quick question here:=0A>> are we planning to rel=
ease from branch-2.9 directly?=0A>>     I doubt this as it seems against ou=
r current branch release practice (=0A>> https://wiki.apache.org/hadoop/How=
ToRelease#Branching). To get rid of=0A>> any confusion, I would suggest to =
cut-off branch-2.9.0 for 2.9.0 release=0A>> work. In the mean time, branch-=
2.9 should be reserved for next 2.9 point=0A>> release (2.9.1) and branch-2=
 should be reserved for next minor release=0A>> (2.10.0 or whatever name it=
 is). Thoughts?=0A>>=0A>> bq. @Junping, lets move the jdiff conversation to=
 separate thread.=0A>> Sure. I will reply jdiff in separated thread.=0A>>=
=0A>> Thanks,=0A>>=0A>> Junping=0A>>=0A>> 2017-10-31 13:44 GMT-07:00 Arun S=
uresh <asuresh@apache.org>:=0A>>=0A>>> Hello folks=0A>>>=0A>>> We just cut =
branch-2.9 since all the critical/blocker issues are now=0A>>> resolved.=0A=
>>> We plan to perform some sanity checks for the rest of the week and cut=
=0A>>> branch-2.9.0 and push out an RC0 by the end of the week.=0A>>>=0A>>>=
 Kindly refrain from committing to branch-2.9 without giving us a heads=0A>=
>> up.=0A>>>=0A>>> @Junping, lets move the jdiff conversation to separate t=
hread.=0A>>>=0A>>> Cheers=0A>>> -Arun/Subru=0A>>>=0A>>> On Mon, Oct 30, 201=
7 at 12:39 PM, Subru Krishnan <subru@apache.org>=0A>>> wrote:=0A>>>=0A>>> >=
 We want to give heads up that we are going to cut branch-2.9 tomorrow=0A>>=
> > morning.=0A>>> >=0A>>> > We are down to 3 blockers and they all are clo=
se to being committed=0A>>> > (thanks everyone):=0A>>> > https://cwiki.apac=
he.org/confluence/display/HADOOP/Hadoop+2.9+Release=0A>>> >=0A>>> > There a=
re 4 other non-blocker JIRAs that are targeted for 2.9.0 which=0A>>> are=0A=
>>> > close to completion.=0A>>> >=0A>>> > Folks who are working/reviewing =
these, kindly prioritize accordingly so=0A>>> > that we can make the releas=
e on time.=0A>>> > https://issues.apache.org/jira/browse/YARN-7398?filter=
=3D12342468=0A>>> >=0A>>> > Thanks in advance!=0A>>> >=0A>>> > -Subru/Arun=
=0A>>> >=0A>>> >=0A>>> >=0A>>>=0A>>=0A>>=0A>


---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org