[HBASE-16422] Tighten our guarantees on compatibility across patch versions - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.0.0
Component/s: documentation
Labels:
None

Release Note:

Hide
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}

Show
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}

Description

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

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HBASE-16422.master.002.patch
16/Aug/16 16:22
3 kB
Michael Stack
HBASE-16422.master.001.patch
16/Aug/16 11:36
3 kB
Michael Stack

Issue Links

links to

Review Board (master)

Activity

People

Assignee:: Michael Stack

Reporter:: Michael Stack

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 16/Aug/16 11:28

Updated:: 19/Aug/16 23:02

Resolved:: 19/Aug/16 23:02