[
https://issues.apache.org/jira/browse/HADOOP-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-7035:
------------------------------
Attachment: jdiff-with-previous-release.sh
Here's a script to generate the incompatible API changes between 0.21.0 and the
0.22 branch. It ignores elements that are marked as @LimitedPrivate or
@Private, and those that are marked as @Evolving or @Unstable. Furthermore, it
uses a modified version of JDiff that only highlights incompatible changes (see
patch at
http://sourceforge.net/tracker/?func=detail&aid=2990626&group_id=37160&atid=419055).
The resulting output can be seen at
http://people.apache.org/~tomwhite/HADOOP-7035/common/docs/jdiff/changes.html
and
http://people.apache.org/~tomwhite/HADOOP-7035/mapreduce/docs/jdiff/changes.html.
(There's no HDFS output because its API is private.)
Should we incorporate this into the release process (so that all changes are
accounted for)? Or have Hudson run it to detect incompatible changes introduced
on a per-patch basis?
> Document incompatible API changes between releases
> --------------------------------------------------
>
> Key: HADOOP-7035
> URL: https://issues.apache.org/jira/browse/HADOOP-7035
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
> Reporter: Tom White
> Attachments: jdiff-with-previous-release.sh
>
>
> We can use JDiff to generate a list of incompatible changes for each release.
> See
> https://issues.apache.org/jira/browse/HADOOP-6668?focusedCommentId=12860017&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12860017
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
