Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Setting JIRA fix versions for 3.0.0 releases
From: Wangda Tan <wheeleast@gmail.com>
In-Reply-To: <CAGHyZ6Lw_B68vvkisCOTj7CgaKH_fN3d0NKM6MKPm8a8Sm4oEw@mail.gmail.com>
Date: Tue, 26 Jul 2016 07:39:15 -0700
Cc: Vinod Kumar Vavilapalli <vinodkv@apache.org>,
 Andrew Wang <andrew.wang@cloudera.com>,
 "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
 "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
 "yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <83B281DA-D462-4E94-9F59-F6E4BA3C33FD@gmail.com>
References: <CAGB5D2YN=rtVZ6yB7ZDXncv5oY0+6GKguRc=0wo+hMrQQJ6zDA@mail.gmail.com> <666A8BE9-1F45-4407-ADD3-84E57931808C@apache.org> <CAGB5D2Z+TAVKRkOC+TGJhe7TbCgHVgm0p=0ySm+ApwcB5KahGQ@mail.gmail.com> <73918F59-AC57-485D-B217-C026E168EB2A@apache.org> <CAGHyZ6+pLZXUz4+2oAevhnfyeXDuR2npaJ=JYRG63Kpxr0EfAA@mail.gmail.com> <CAD++eC=0pLf4JDCw8t=JjMcNV1WhuNoCacfBz5dxsUMNYAAD=w@mail.gmail.com> <CAD++eCmNJQB7YkGAkOWuvMEWTAFh=DQEszPjAjfG63xk881J=w@mail.gmail.com> <CAGHyZ6Lw_B68vvkisCOTj7CgaKH_fN3d0NKM6MKPm8a8Sm4oEw@mail.gmail.com>
To: Sean Busbey <busbey@cloudera.com>
archived-at: Tue, 26 Jul 2016 14:39:32 -0000

Hi Sean,
Sorry I didn't make it clear, lets try to use both jdiff and the new tool an=
d compare results because this is the first time with the new tool.

Appreciate your time to help us about this effort!

Thanks,
Wangda

Sent from my iPhone

> On Jul 26, 2016, at 6:01 AM, Sean Busbey <busbey@cloudera.com> wrote:
>=20
> Just so I don't waste time chasing my tail, should I interpret this
> email and the associated JIRA as the PMC preferring I not spend
> volunteer time providing a compatibility breakdown as previously
> discussed?
>=20
>> On Mon, Jul 25, 2016 at 7:54 PM, Wangda Tan <wheeleast@gmail.com> wrote:
>> I just filed ticket https://issues.apache.org/jira/browse/HADOOP-13423 to=

>> track running JDIFF on trunk and analyze results for Hadoop-common. I wil=
l
>> work on that and keep the JIRA and this thread updated. We need to do the=

>> same work for YARN/MR/HDFS.
>>=20
>>> On Mon, Jul 25, 2016 at 5:47 PM, Wangda Tan <wheeleast@gmail.com> wrote:=

>>>=20
>>> I agree with what Vinod mentioned: we need to revisit all incompatible
>>> changes and revert unnecessary ones. Even if we don't have any compatibi=
lity
>>> guarantees between 2.x and 3.x. But make user to be less frustrated whil=
e
>>> trying 3.x is always a better option to me.
>>>=20
>>> To achieve this we need to run jdiff for trunk and look at results. I
>>> would suggest to do this before 3.0.0-alpha1 release.
>>>=20
>>> In addition, for people who will try this 3-alpha1 release artifacts, a
>>> guide about migration from 2.x to 3.x will be very helpful, and it can a=
lso
>>> help for people to better understand what have changed (Just like
>>> http://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-map=
reduce-client-core/MapReduce_Compatibility_Hadoop1_Hadoop2.html)
>>>=20
>>> Thoughts?
>>>=20
>>> Thanks,
>>> Wangda
>>>=20
>>>=20
>>>> On Thu, Jul 21, 2016 at 2:41 PM, Sean Busbey <busbey@cloudera.com> wrot=
e:
>>>>=20
>>>> On Thu, Jul 21, 2016 at 4:32 PM, Vinod Kumar Vavilapalli
>>>> <vinodkv@apache.org> wrote:
>>>>>> I really, really want a 3.0.0-alpha1 ASAP, since it's basically
>>>>>> impossible for downstreams to test incompat changes and new features w=
ithout
>>>>>> a release artifact. I've been doing test builds, and branch-3.0.0-alp=
ha1 is
>>>>>> ready for an RC besides possibly this fix version issue.
>>>>>=20
>>>>> Not arguing against the need for an alpha release, the question is if
>>>>> it can wait till after 2.8 gets done.
>>>>>=20
>>>>> Orthogonally, do we have a report of the incompatible changes? Like th=
e
>>>>> one I generated for some of the branch-2 releases using late jdiff wor=
k from
>>>>> Li Lu etc. We should do this and fix any inadvertant incompatibilities=
.
>>>>> Without seeing this list of incompatibilities, why even make an alpha
>>>>> release and force downstream components to discover issues what can be=

>>>>> identified through running reports.
>>>>=20
>>>> I can come up with this, atleast for Source / Binary API compatibility,=

>>>> provided folks don't mind if I use the Java API Compliance Checker[1]
>>>> instead of jdiff.
>>>>=20
>>>> I'm already familiar with quickly using it, esp with Audience
>>>> Annotations from my work in HBase.
>>>>=20
>>>> Do you want this check from some particular branch-2 release? It
>>>> matters since the releases along branch-2 have themselves had some
>>>> noise[2].
>>>>=20
>>>> [1]: https://github.com/lvc/japi-compliance-checker
>>>> [2]: http://abi-laboratory.pro/java/tracker/timeline/hadoop/
>>>>=20
>>>> --
>>>> busbey
>>>>=20
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>=20
>=20
>=20
> --=20
> busbey

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