[
https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771283#comment-13771283
]
Aleksandr Shulman commented on HBASE-9153:
------------------------------------------
Hey Nick, thanks for the commit.
In terms of release note, here is what I propose:
"Added a tool to generate a report of API compatibility between different
versions of hbase. It is found in dev-support and uses JDiff under the covers.
Usage info at the top of the script."
I'm not sure if this is exactly what you're looking for, but we can adjust as
necessary.
> Introduce/update a script to generate jdiff reports
> ---------------------------------------------------
>
> Key: HBASE-9153
> URL: https://issues.apache.org/jira/browse/HBASE-9153
> Project: HBase
> Issue Type: Task
> Reporter: Jonathan Hsieh
> Assignee: Aleksandr Shulman
> Fix For: 0.98.0, 0.96.0
>
> Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch,
> HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch,
> HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch,
> HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch,
> HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch
>
>
> We've had a few issues now where we've removed API's without deprecating or
> deprecating in the late release. (HBASE-9142, HBASE-9093) We should just
> have a tool that enforces our api deprecation policy as a release time check
> or as a precommit check.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
