[
https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4403:
-------------------------
Resolution: Fixed
Fix Version/s: (was: 0.94.0)
0.96.0
Release Note: Adds stability and audience classification annotations on
all classes
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk. Also added doc. to the guide. Thanks for the fat patch
Jimmy. I wish it was you who was committing it rather than me because everyone
is going to hate me rather than you for breaking all of their outstanding
patches (smile). Good stuff.
> 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
> Fix For: 0.96.0
>
> Attachments: hbase-4403-interface.txt, hbase-4403-interface_v2.txt,
> hbase-4403-interface_v3.txt, hbase-4403-nowhere-near-done.txt,
> hbase-4403.patch, hbase-4403.patch
>
>
> 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
