hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@apache.org>
Subject Re: Setting JIRA fix versions for 3.0.0 releases
Date Mon, 25 Jul 2016 20:47:05 GMT
Actually, I wouldn’t trust this report as it stands today at all.

I quickly glanced the report, looking for what it highlights as incompatible. But the ones
that I saw have private / visible for testing annotations. Other than acting as useless evidence
for those lashing out on branch-2, this won’t do much good.

Whenever we start working towards switching to this tool, it should incorporate the same exclude-annotations
logic that the jdiff code-path does today. Do you think that is possible?


> On Jul 22, 2016, at 4:53 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org> wrote:
>> 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].
>> [1]: https://github.com/lvc/japi-compliance-checker <https://github.com/lvc/japi-compliance-checker>
<https://github.com/lvc/japi-compliance-checker <https://github.com/lvc/japi-compliance-checker>>
>> [2]: http://abi-laboratory.pro/java/tracker/timeline/hadoop/ <http://abi-laboratory.pro/java/tracker/timeline/hadoop/>
<http://abi-laboratory.pro/java/tracker/timeline/hadoop/ <http://abi-laboratory.pro/java/tracker/timeline/hadoop/>>
>> -- 
>> busbey

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message