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:08:41 GMT

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

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

GitHub user hanm opened a pull request:

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

    ZOOKEEPER-2635: regenerate document for master / 3.6 branch.

    

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

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

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

    https://github.com/apache/zookeeper/pull/203.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 #203
    
----
commit b26eea2df5ce0f1fe16fbcc4489c0dee16d46f0d
Author: Michael Han <hanm@apache.org>
Date:   2017-03-21T19:07:15Z

    ZOOKEEPER-2635: regenerate document for master / 3.6 branch.

----


> 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
(v6.3.15#6346)

Mime
View raw message