You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Igor Galić (Created JIRA)" <ji...@apache.org> on 2011/12/16 10:44:30 UTC
[jira] [Created] (INFRA-4225) Migration of Traffic Server's site to
cms
Migration of Traffic Server's site to cms
-----------------------------------------
Key: INFRA-4225
URL: https://issues.apache.org/jira/browse/INFRA-4225
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: CMS
Reporter: Igor Galić
Hi folks,
I would like to migrate the Traffic Server site to the one we've been hacking on in branches/ats-cms
For this effect I'd like to migrate the old content docs into branches/ats-cms/docs/v2 first, without causing any disruption (this would need to be {{svn mv}}-ed) - so I suppose we need to disable SvnPubSub first.
Then I would move the entire branch into trunk.
Does this sound like a reasonable plan? - When can we do this?
Thank you in advance!
So long,
i
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-4225) Migration of Traffic Server's site to
cms
Posted by "Joe Schaefer (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Schaefer closed INFRA-4225.
-------------------------------
Resolution: Fixed
resolved last night.
> Migration of Traffic Server's site to cms
> -----------------------------------------
>
> Key: INFRA-4225
> URL: https://issues.apache.org/jira/browse/INFRA-4225
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Igor Galić
>
> Hi folks,
> I would like to migrate the Traffic Server site to the one we've been hacking on in branches/ats-cms
> For this effect I'd like to migrate the old content docs into branches/ats-cms/docs/v2 first, without causing any disruption (this would need to be {{svn mv}}-ed) - so I suppose we need to disable SvnPubSub first.
> Then I would move the entire branch into trunk.
> Does this sound like a reasonable plan? - When can we do this?
> Thank you in advance!
> So long,
> i
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira