[
https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-4403:
-------------------------------
Attachment: hbase-4403-interface_v2.txt
I got some distraction. Here is the v2 I have so far. I already added
MiniZookeeper cluster as public, Evolving. I'd like to add MiniHBaseCluster as
well but it is in test folder.
Do we classify those classes in test folder? Should we move them to the main
folder?
> Adopt interface stability/audience classifications from Hadoop
> --------------------------------------------------------------
>
> Key: HBASE-4403
> URL: https://issues.apache.org/jira/browse/HBASE-4403
> Project: HBase
> Issue Type: Task
> Affects Versions: 0.90.5, 0.92.0
> Reporter: Todd Lipcon
> Assignee: Jimmy Xiang
> Attachments: hbase-4403-interface.txt, hbase-4403-interface_v2.txt,
> hbase-4403-nowhere-near-done.txt
>
>
> As HBase gets more widely used, we need to be more explicit about which APIs
> are stable and not expected to break between versions, which APIs are still
> evolving, etc. We also have many public classes that are really internal to
> the RS or Master and not meant to be used by users. Hadoop has adopted a
> classification scheme for audience (public, private, or limited-private) as
> well as stability (stable, evolving, unstable). I think we should copy these
> annotations to HBase and start to classify our public classes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
