[
https://issues.apache.org/jira/browse/HADOOP-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540480
]
Doug Cutting commented on HADOOP-2160:
--------------------------------------
After we do this, the Hadoop subversion tree should look something like:
{noformat}
hadoop/
branches/
tags/
trunk/
docs/ -- generated html of user documentation
src/
docs/ -- source files of user documentation
site/
author/ -- source files of website
publish/ -- generated html of website
{noformat}
Then our published website directory
(people.apache.org:/www/lucene.apache.org/) would have the following things
checked out from subversion to create the production site:
{noformat}
hadoop/ -- http://svn.apache.org/repos/asf/lucene/hadoop/site/publish
0.15.0/ --
http://svn.apache.org/repos/asf/lucene/hadoop/tags/release-0.15.0/docs
0.14.3/ --
http://svn.apache.org/repos/asf/lucene/hadoop/tags/release-0.14.3/docs
{noformat}
The site pages would link to the version-specific user documentation through
relative links that assume this deployment structure.
Does this sound reasonable?
> separate website from user documentation
> ----------------------------------------
>
> Key: HADOOP-2160
> URL: https://issues.apache.org/jira/browse/HADOOP-2160
> Project: Hadoop
> Issue Type: Improvement
> Reporter: Doug Cutting
>
> Currently the website only contains the documentation for a single release,
> the current release. It would be better if the website also contained
> documentation for past releases, since not everyone is using the current
> release. To implement this we should move the top-level of the website,
> including project and developer information, from the subversion trunk into a
> separate tree, so that only the user documentation is branched per release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
