[
https://issues.apache.org/jira/browse/WHIRR-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529842#comment-13529842
]
Tom White commented on WHIRR-685:
---------------------------------
I suggest we put the site contents under
http://svn.apache.org/repos/asf/whirr/site/production. There are two parts to
the site - the top-level site generated from
http://svn.apache.org/repos/asf/whirr/site/src, and the documents for each
release generated from the main project repo at
http://svn.apache.org/repos/asf/whirr/trunk. The site generation procedure
would change so that the generated files from each part would be copied to a
checked out version of http://svn.apache.org/repos/asf/whirr/site/production.
To publish, the changes would simply be checked in, which would trigger the
svnpubsub process.
Once we have got the current site in svn we can open an infra ticket
https://issues.apache.org/jira/browse/INFRA to ask for the site to be published
using svnpubsub (they can't do anything until there's a svn URL,
http://www.apache.org/dev/infra-contact#what-we-need-to-know).
Does that sound good?
> Add Whirr website to svn
> ------------------------
>
> Key: WHIRR-685
> URL: https://issues.apache.org/jira/browse/WHIRR-685
> Project: Whirr
> Issue Type: Task
> Components: build, documentation
> Reporter: Tom White
> Assignee: Tom White
> Priority: Critical
>
> To migrate to svnpubsub we need to have the website checked into svn (note
> that git isn't supported for websites, see
> http://www.apache.org/dev/project-site.html). Currently it is not checked in,
> since we just generate the site with mvn and copy it to a directory on
> people.apache.org. This mechanism will be removed at the end of this month.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
