hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Shulman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9153) Create a deprecation policy enforcement check
Date Fri, 06 Sep 2013 01:02:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759717#comment-13759717

Aleksandr Shulman commented on HBASE-9153:

The usage is a little confusing. The arguments come in pairs. So if you specify a local source
dir for $1, then $2 is the name of that code. It's arbitrary. The same is true for 3 and 4,
respectively. If you specify a git repo as argument $1 or argument $3, then arguments $2 or
$4, respectively, is the name of the branch. This is not arbitrary.
In either case, arguments $2 and $4 are used as labels in the report.

You can have two references from the same git repo, but you'd have to specify it twice, once
as argument $1 and once as argument $3.

{quote}how do I specify a local repo{quote}
You can use the absolute location of the /hbase folder. So if my code path looked like /home/aleks/code/hbase/0.95/hbase/hbase-server/...
then I would give /home/aleks/code/hbase/0.95/hbase as the argument.

{quote}I'm seeing lots of errors{quote}
I have seen it as well. I don't know the cause but the resulting reports look correct and
it doesn't cause the operation to fail. 
We should look into it is being generated, however.

Also, the script will appear to hang at times, but it's not actually hanging. Note that it
takes ~30 minutes to do a run.

> 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

View raw message