Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 27 Aug 2013 09:05:51 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12662414.1375891013061.38429.1377594351905@arcas>
In-Reply-To: <JIRA.12662414.1375891013061@arcas>
References: <JIRA.12662414.1375891013061@arcas>
Subject: [jira] [Commented] (HBASE-9153) Create a deprecation policy
 enforcement check
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-9153:
---------------------------------------

This is git only? Fine by me but we have a SVN based process so should be SVN to be a general project tool? 

Maybe it's better to not name things by or mention the singularity if it is to be a tool for use by any RM at every release?
                
> 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
>
>
> 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