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

ASF GitHub Bot commented on ZOOKEEPER-2829:
-------------------------------------------

GitHub user afine opened a pull request:

    https://github.com/apache/zookeeper/pull/317

    ZOOKEEPER-2829: Interface usability / compatibility improvements through 
Java annotation.

    See https://github.com/apache/zookeeper/pull/316

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/afine/zookeeper ZOOKEEPER-2829_3.4

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zookeeper/pull/317.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #317
    
----
commit ae43aeaca890f868123badbdffd3803f9df012d7
Author: Abraham Fine <[email protected]>
Date:   2017-07-24T22:36:32Z

    ZOOKEEPER-2829: Interface usability / compatibility improvements through 
Java annotation.

----


> Interface usability / compatibility improvements through Java annotation.
> -------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2829
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2829
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: java client, server
>    Affects Versions: 3.4.10, 3.5.3
>            Reporter: Michael Han
>            Assignee: Abraham Fine
>              Labels: annotation
>
> Hadoop has interface classification regarding the interfaces' scope and 
> stability. ZK should do something similar, which not only provides additional 
> benefits of making API compatibility easier between releases (or even 
> commits, by automating the checks via some tooling), but also consistent with 
> rest of Hadoop ecosystem.
> See HADOOP-5073 for more context.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to