tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "JaeHwa Jung (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-322) Documentation by version
Date Fri, 22 Nov 2013 02:12:37 GMT

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

JaeHwa Jung commented on TAJO-322:
----------------------------------

+1
I also think that we need to manage documents by release version.


> Documentation by version
> ------------------------
>
>                 Key: TAJO-322
>                 URL: https://issues.apache.org/jira/browse/TAJO-322
>             Project: Tajo
>          Issue Type: Task
>          Components: documentation
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.8-incubating
>
>         Attachments: TAJO-322.patch
>
>
> Currently, the documentation is based on Wiki. After releases, we need to keep some document
snapshot available in online. The wiki page is not good for this purpose.
> So, I would like to suggest that user documentation moves to static htmls and keep developer
document in the current wiki. In addition, we should keep static htmls for each version in
Tajo site.
> This patch contains a markdown document used to generate static user document html for
0.2 and 0.8, and update the site for this change.
> You can see the draft at http://people.apache.org/~hyunsik/tajo/tajo-0.2.0-doc.html.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message