[
https://issues.apache.org/jira/browse/ZOOKEEPER-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105100#comment-17105100
]
Zili Chen edited comment on ZOOKEEPER-3792 at 5/12/20, 5:46 AM:
----------------------------------------------------------------
Hi [~symat]! You're the release manager so I think it would be better you take
over the ticker for verifying it in the release process.
You can make use of the linked PR whose idea is mainly "generate aggregate java
apidoc". FYI, previously we only delivered zookeeper-server java apidoc, and
the manner seems changed with
ZOOKEEPER-3369(a2aecb9acc420c95f60b6649ffcbd4e0184cc0cd).
was (Author: tison):
Hi [~symat]! You're the release manager and I think it would be better you take
over the ticker for verifying it in the release process.
You can make use of the linked PR whose idea is mainly "generate aggregate java
apidoc". FYI, previously we only delivered zookeeper-server java apidoc, and
the manner seems changed with
ZOOKEEPER-3369(a2aecb9acc420c95f60b6649ffcbd4e0184cc0cd).
> Reconcile document site in 3.5.7 & 3.6.0
> ----------------------------------------
>
> Key: ZOOKEEPER-3792
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3792
> Project: ZooKeeper
> Issue Type: Bug
> Components: documentation
> Affects Versions: 3.6.0, 3.5.7
> Reporter: Zili Chen
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After ZOOKEEPER-3369 we generate document in {{apidocs/}} instead of {{api/}}
> before. Moreover, the document site cannot proper linked to apidocs in
> 3.6.0(but in 3.5.7, thought it is wrong in {{website}} branch, it is manually
> corrected in {{asf-site}} branch}}.
> I propose we generate single aggregated document and place it under {{api/}}
> folder, as well as bumping website for the update.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
