www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Fisher (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-5408) OpenOffice TLP: Website
Date Tue, 13 Nov 2012 00:41:12 GMT

    [ https://issues.apache.org/jira/browse/INFRA-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495794#comment-13495794

David Fisher commented on INFRA-5408:

Whatever is done will need to be svn moves and svnwcsub changes.

Following Daniel's alternatives:
(a) stop svnwcsub on /www/incubator.a.o/content/ooo
(b) start svnwcsub on /www/openoffice.a.o
(c) svn move the site source + full rebuild + publish.
(d) infra removes httpd.conf redirect (zzzother?)
(e) assure redirection of i.a.o/openofficeorg/ to oo.a.o/ via infra preferred method (is this
zzzother too and not .htaccess?)

Then committers can do svn switch --relocate on existing checkouts and/or continue to make
use of the Apache CMS.

We should warn the community to commit and then avoid anonymous cms changes to the project

For openoffice.org the process differs:
(a) stop svnwcsub on /www/oo.o/content/
(b) svn move the site source.
(c) edit the site config to change the site source for oo.o.
(e) start svnwcsub on /www/oo.o/content/
(f) full rebuild + publish.

But the same warnings and relocations apply.

> OpenOffice TLP: Website
> -----------------------
>                 Key: INFRA-5408
>                 URL: https://issues.apache.org/jira/browse/INFRA-5408
>             Project: Infrastructure
>          Issue Type: Sub-task
>      Security Level: public(Regular issues) 
>          Components: TLP Admin
>            Reporter: David Fisher
> Please set up OpenOffice TLP website structure. 
> Rave is using the CMS and the site is currently published to 
> http://incubator.apache.org/openofficeorg
> please change to 
> http://openoffice.apache.org

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

View raw message