hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] Commented: (HIVE-1135) Use Anakia for version controlled documentation
Date Fri, 18 Jun 2010 19:59:24 GMT


Edward Capriolo commented on HIVE-1135:

Great on ivy. 
As for the wiki I think we should just put a node at the top of the page that says "Do not
edit me. Edit xdocs instead." For the pages we have migrated. I want to do like a page every
other day so it should be done soon enough. I actually have commit access but I usually leave
the commits up to the experts. Also since I worked on this ticket I really should not be the
commit person. Anyone else?

> Use Anakia for version controlled documentation
> -----------------------------------------------
>                 Key: HIVE-1135
>                 URL:
>             Project: Hadoop Hive
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 0.5.0
>            Reporter: Edward Capriolo
>            Assignee: Edward Capriolo
>             Fix For: 0.6.0
>         Attachments: hive-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt,
hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE,
> Currently the Hive Language Manual and many other critical pieces of documentation are
on the Hive wiki. 
> Right now we count on the author of a patch to follow up and add wiki entries. While
we do a decent job with this, new features can be missed. Or using running older/newer branches
can not locate relevant documentation for their branch. 
> ..example of a perception I do not think we want to give off...
> We should generate our documentation in the way hadoop & hbase does, inline using
forest. I would like to take the lead on this, but we need a lot of consensus on doing this

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message