hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-20149) Purge dev javadoc from bin tarball (or make a separate tarball of javadoc)
Date Tue, 10 Apr 2018 17:14:00 GMT

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

stack commented on HBASE-20149:

Pushed to branch-2.0+.

Thanks [~busbey]. Pasting your list into release notes. When you say 'published on the website',
it makes it sound like we have an automated process rather than the manual hackery we currently
do -- but I'll buy it.

Wondering now if we should publish dev and user doc and no test APIs.

HBASE-19663 makes it so user and dev api are currently the same thing when you click 'User
API' and 'Dev API'. Needs work.

> Purge dev javadoc from bin tarball (or make a separate tarball of javadoc)
> --------------------------------------------------------------------------
>                 Key: HBASE-20149
>                 URL: https://issues.apache.org/jira/browse/HBASE-20149
>             Project: HBase
>          Issue Type: Sub-task
>          Components: build, community, documentation
>            Reporter: stack
>            Assignee: Artem Ervits
>            Priority: Critical
>             Fix For: 2.0.0
>         Attachments: HBASE-20149.branch-2.0.001.patch, HBASE-20149.branch-2.0.002.patch,
> The bin tarball is too fat (Chia-Ping and Josh noticed it on the beta-2 vote). A note
to the dev list subsequently resulted in suggestion that we just purge dev javadoc (or even
all javadoc) from bin tarball (Andrew). Sean was good w/ it and suggested perhaps we could
do a javadoc only tgz. Let me look into this.

This message was sent by Atlassian JIRA

View raw message