zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2635) Regenerate documentation
Date Tue, 21 Mar 2017 19:05:41 GMT

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

ASF GitHub Bot commented on ZOOKEEPER-2635:

GitHub user hanm opened a pull request:


    ZOOKEEPER-2635: regenerate document for branch-3.5 before release.

    Will create a separate PR for master (though there is not much need, but previous commit
by Flavio also updated doc for master, so just for completeness sake.).
    I don't believe anyone is going to review bin diffs by naked eye, so I am going to merge
this right away.

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

    $ git pull https://github.com/hanm/zookeeper ZOOKEEPER-2635

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


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

    This closes #202
commit e91834f25187c6cc175021038691df1a49160d5e
Author: Michael Han <hanm@apache.org>
Date:   2017-03-21T19:03:09Z

    ZOOKEEPER-2635: regenerate document for branch-3.5 before release.


> Regenerate documentation
> ------------------------
>                 Key: ZOOKEEPER-2635
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2635
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Flavio Junqueira
>            Assignee: Michael Han
>            Priority: Blocker
>             Fix For: 3.5.3, 3.6.0
> Some recent commits did not regenerate the documentation even though they had documentation
changes, we need to do it before releasing.

This message was sent by Atlassian JIRA

View raw message