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

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

GitHub user eribeiro opened a pull request:

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

    ZOOKEEPER-2552: Revisit release doc and remove the issues not covered by 
release

    

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

    $ git pull https://github.com/eribeiro/zookeeper ZOOKEEPER-2552

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

    https://github.com/apache/zookeeper/pull/124.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 #124
    
----
commit 0fd4ca143499cafc8a7090f2dea32f733ccd08d8
Author: Edward Ribeiro <edward.ribe...@gmail.com>
Date:   2016-12-14T19:09:52Z

    ZOOKEEPER-2552: Revisit release note doc and remove the items which are not 
related to the released version

----


> Revisit release note doc and remove the items which are not related to the 
> released version
> -------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2552
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2552
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Rakesh R
>            Assignee: Edward Ribeiro
>             Fix For: 3.4.10
>
>         Attachments: ZOOKEEPER-2552.patch, closed.py
>
>
> Couple of issues listed on http://zookeeper.apache.org/
> doc/r3.4.9/releasenotes.html that are either 'Open' or 'Patch available'. For 
> example, issues were wrongly marked as "3.4.8" fix version in jira and has 
> caused the trouble.
> This jira to cross check all the jira issues present in the release note and 
> check the correctness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to