[
https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759392#comment-13759392
]
Aleksandr Shulman commented on HBASE-9153:
------------------------------------------
{quote}These are the steps I was expecting. Do you plan to include those as
further patch revisions on this ticket or open followup tickets?{quote}
That's a good question. I did a first-pass at steps 1 and 2 and I could not
find a quick one-off to the tool to allow that. Therefore, it'll probably
involve a non-trivial amount of work. That said, they are on my back-burner.
Meanwhile, it would be great if other folks wanted to maybe take a look.
{quote}Indeed. And here I thought you were doing to reveal some of the secret
sauce behind your recent blog post {quote}
:)
> 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,
> HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-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
