[
https://issues.apache.org/jira/browse/HBASE-16422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-16422.
---------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Release Note:
Adds below change to our compat guarantees:
{code}
-* Example: A user using a newly deprecated api does not need to modify
application code with hbase api calls until the next major version.
10 +* New APIs introduced in a patch version will only be added in a source
compatible way footnote:[See 'Source Compatibility'
https://blogs.oracle.com/darcy/entry/kinds_of_compatibility]: i.e. code
that implements public APIs will continue to compile.
{code}
> Tighten our guarantees on compatibility across patch versions
> -------------------------------------------------------------
>
> Key: HBASE-16422
> URL: https://issues.apache.org/jira/browse/HBASE-16422
> Project: HBase
> Issue Type: Improvement
> Components: documentation
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0
>
> Attachments: HBASE-16422.master.001.patch,
> HBASE-16422.master.002.patch
>
>
> Out of the dev discussion [1], comes this change that tightens up our
> guarantees adding new API; that we'll do it in a non-breaking way across
> patch versions.
> 1. http://mail-archives.apache.org/mod_mbox/hbase-dev/201608.mbox/browser
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
