You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Joshua Slive (JIRA)" <ji...@apache.org> on 2006/06/12 18:15:31 UTC
[jira] Commented: (INFRA-843) final items to complete tapestry move
from jakarta to TLP
[ http://issues.apache.org/jira/browse/INFRA-843?page=comments#action_12415873 ]
Joshua Slive commented on INFRA-843:
------------------------------------
For the websites, you just need to drop an .htaccess files in the appropriate directories with something like
Redirect pemanent /tapestry/ http://tapestry.apache.org/
For the dist directories, you should just move them and drop a README in the old directory pointing to the new location. At some point you might want to clean up archives.apache.org/dist as well.
> final items to complete tapestry move from jakarta to TLP
> ---------------------------------------------------------
>
> Key: INFRA-843
> URL: http://issues.apache.org/jira/browse/INFRA-843
> Project: Infrastructure
> Type: Task
> Security: public(Regular issues)
> Components: TLP Admin
> Environment: minotaur
> Reporter: Jesse Kuhnert
>
> The new TLP site is mostly complete, http://tapestry.apache.org. The old documentation for tapestry has been copied over to the new /www/tapestry.apache.org directories.
> The outstanding items I'm not sure how to handle still are:
> -) How to handle migrating existing bookmarks/users over to the new site? Can we setup a global html page with some text like "Tapestry has moved to tapestry.apache.org, your browser will be redirected in N seconds..." ?
> -) What to do about old download directories/jakarta site history listing those releases?
> -) What to do about jakarta site in general..Does it the move get a news item and the link taken out or...?
> Those are the only migratory issues I can think of right now. I still need to get final approval from Howard Lewis-Ship before anything permanent is done but we can at least establish what the general plan of action is now.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira