[
https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759332#comment-13759332
]
Aleksandr Shulman commented on HBASE-9153:
------------------------------------------
Hi [~ndimiduk], I haven't attached the patch yet. I will do so shortly.
You're correct in that the checkin does not do any enforcement, nor does it
have an automatic way to detect incompatible changes. These are potential next
steps.
Other next steps:
1. Have JDiff only examine a specific set of classes/packagages that are
client-facing.
2. Have it raise an alert anytime something incompatible is introduced.
2a. Have it mute known incompatibilities
3. Add it as a pre-checkin hook
Finally, I recall you had a question about text format. So far I haven't found
a way to generate a text-only format. It would definitely be useful for parsing
and so forth!
> Create a deprecation policy enforcement check
> ---------------------------------------------
>
> Key: HBASE-9153
> URL: https://issues.apache.org/jira/browse/HBASE-9153
> Project: HBase
> Issue Type: Task
> Reporter: Jonathan Hsieh
> Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.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
