[
https://issues.apache.org/jira/browse/HADOOP-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting resolved HADOOP-4920.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.20.0
Assignee: Doug Cutting
I just committed this.
Should we merge this to the 0.19 branch? We will have to adjust release
procedures a bit, since the docs for releases will not be in subversion, on the
website, they must now, like javadoc, be unpacked from the release rather than
retrieved from a subversion tag. Perhaps better to address this now, while
it's fresh in our minds, rather than when we get to 0.20? Nigel?
> do not keep forrest output in subversion
> ----------------------------------------
>
> Key: HADOOP-4920
> URL: https://issues.apache.org/jira/browse/HADOOP-4920
> Project: Hadoop Core
> Issue Type: Improvement
> Components: documentation
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 0.20.0
>
> Attachments: HADOOP-4920.patch, HADOOP-4920.sh
>
>
> We currently re-generate PDF and HTML documentation whenever we commit a
> documentation patch, which creates huge commit messages that few read. This
> was
> originally done so that folks who check out the sources from subversion did
> not
> need to install forrest in order to read the documentation.
> Note, this issue only concerns the versioned documentation included in trunk
> and releases, not the website, whose forrest output should continue to be
> kept in subversion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
